# The CPU is not scaling with high search load in Elasticsearch7.3.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [August 12, 2019, 3:27pm UTC](https://discuss.elastic.co/t/the-cpu-is-not-scaling-with-high-search-load-in-elasticsearch7-3-0/194873 "2019-08-12T15:27:22Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![suvarna](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@suvarna](https://discuss.elastic.co/u/suvarna)\ **Post date:** [August 12, 2019, 3:27pm UTC](https://discuss.elastic.co/t/the-cpu-is-not-scaling-with-high-search-load-in-elasticsearch7-3-0/194873/1 "2019-08-12T15:27:22Z")
Hi We have numa enabled server with 2 sockets, each socket with 28 cores and its one node cluster with 10 indies , 5 shards each. Under the same workload(with high search operation load): **Scenario 1** when we run ES7.3.0 on both the sockets , we can see CPU utilization is 30% , search throughput is 1700 ops/sec and when we increased the search load, the CPU utilization is not going beyond 30%. and throughput is also not going beyond 1700 ops/sec. Is there any Elasticsearch specific settings which is restricting to use all available CPU's on high search load? **Scenario 2:** When we bind ES7.3.0 to one socket we can see all the CPU's were utilized around 90 to 95%. and the ops/sec is 2550 ops/sec which is more then 1700 ops/sec. Please let me know, in case of 2 sockets why the CPU is not scaling even with high search load. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 9, 2019, 3:27pm UTC](https://discuss.elastic.co/t/the-cpu-is-not-scaling-with-high-search-load-in-elasticsearch7-3-0/194873/2 "2019-09-09T15:27:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.