# Why elastic node use only 50-60 % of cpu?

**URL:** <https://discuss.elastic.co/t/why-elastic-node-use-only-50-60-of-cpu/184463>\
**Category:** Elasticsearch\
**Created:** [June 5, 2019, 10:22pm UTC](https://discuss.elastic.co/t/why-elastic-node-use-only-50-60-of-cpu/184463 "2019-06-05T22:22:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tfe2012](https://avatars.discourse-cdn.com/v4/letter/t/49beb7/32.png) [@tfe2012](https://discuss.elastic.co/u/tfe2012)\
**Post date:** [June 5, 2019, 10:22pm UTC](https://discuss.elastic.co/t/why-elastic-node-use-only-50-60-of-cpu/184463/1 "2019-06-05T22:22:29Z")

</div>

Hi, I have a cluster of 1 coordinator and 16 data node. 48 shard 1 replica. 1.4 TB data.

I send a request like:

```auto
GET twitter/_search
{
  "query": {
    "term": {
      "url": "https://twitter/twit"
    }
  }
}

```

Kibana looks like this:

 ![53](https://us1.discourse-cdn.com/elastic/original/3X/7/2/72124602312ecc0f4b4cf6a4a78d0f20c39655fd.png)

Us result I reach 4000 request/second. Is it anyway how to improve this number?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 5, 2019, 10:24pm UTC](https://discuss.elastic.co/t/why-elastic-node-use-only-50-60-of-cpu/184463/2 "2019-06-05T22:24:06Z")

</div>

Improve it to what? Is the search slow?  
Why do you want 100% of your CPU being used?

---

<div class="post-metadata">

**Author:** ![tfe2012](https://avatars.discourse-cdn.com/v4/letter/t/49beb7/32.png) [@tfe2012](https://discuss.elastic.co/u/tfe2012)\
**Post date:** [June 5, 2019, 10:37pm UTC](https://discuss.elastic.co/t/why-elastic-node-use-only-50-60-of-cpu/184463/3 "2019-06-05T22:37:14Z")

</div>

I want reach 20 000 - 40 000 request's per second.

But don't know how. I need

1. change config ?
2. add more data nodes ?
3. add more coordinators ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 5, 2019, 10:58pm UTC](https://discuss.elastic.co/t/why-elastic-node-use-only-50-60-of-cpu/184463/4 "2019-06-05T22:58:04Z")

</div>

How are you send the requests to Elasticsearch?  
What sort of data is it?  
Is that query all you are doing?  
Have you done benchmarking?

---

<div class="post-metadata">

**Author:** ![tfe2012](https://avatars.discourse-cdn.com/v4/letter/t/49beb7/32.png) [@tfe2012](https://discuss.elastic.co/u/tfe2012)\
**Post date:** [June 5, 2019, 11:02pm UTC](https://discuss.elastic.co/t/why-elastic-node-use-only-50-60-of-cpu/184463/5 "2019-06-05T23:02:32Z")

</div>

1. sending using java client . port 9300

2. Documents are like:

```auto
{
        "_index" : "twitter",
        "_type" : "twitter",
        "_id" : "5280F4F01D6A6F7CE386E1D135CD3162",
        "_score" : 15.434762,
        "_source" : {
          "urls" : [
            "https://twitter/twit",
            "/twit"
          ],
          "fullname" : "Test name",
          "url" : "https://twitter/twit"
        }
      }

```

1. I scroll index and only send tem request.

2. no

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 3, 2019, 11:02pm UTC](https://discuss.elastic.co/t/why-elastic-node-use-only-50-60-of-cpu/184463/6 "2019-07-03T23:02:36Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.