# Multiple core cpu

**URL:** <https://discuss.elastic.co/t/multiple-core-cpu/113648>\
**Category:** Elasticsearch\
**Created:** [December 31, 2017, 3:46am UTC](https://discuss.elastic.co/t/multiple-core-cpu/113648 "2017-12-31T03:46:39Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![hoang2117](https://avatars.discourse-cdn.com/v4/letter/h/6de8d8/32.png) [@hoang2117](https://discuss.elastic.co/u/hoang2117)\
**Post date:** [December 31, 2017, 3:46am UTC](https://discuss.elastic.co/t/multiple-core-cpu/113648/1 "2017-12-31T03:46:39Z")

</div>

I have problems with multiple cpu cores use.  
My server have 12cores and available everytime, but on the peak time it be stuck because Elasticserach cannot use more than one core.  
I check process by top command and see only one core have load 150-200%  
Cannot change config to use more than one core ☹

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 31, 2017, 9:12am UTC](https://discuss.elastic.co/t/multiple-core-cpu/113648/2 "2017-12-31T09:12:50Z")

</div>

What is your use case? Is it indexing or query heavy? How many shards and indices do you have? Is there anything else limiting performance, e.g. disk I/O?

---

<div class="post-metadata">

**Author:** ![hoang2117](https://avatars.discourse-cdn.com/v4/letter/h/6de8d8/32.png) [@hoang2117](https://discuss.elastic.co/u/hoang2117)\
**Post date:** [December 31, 2017, 10:16am UTC](https://discuss.elastic.co/t/multiple-core-cpu/113648/3 "2017-12-31T10:16:06Z")

</div>

I have ubuntu server with 12 cores cpu . 70GB RAM. SSD Disk  
On this server i running

- nginx server
- ELK
- uwsgi django application  
I config for nginx and uwsgi to use maximum of cores. On the peak time, almost cpu have load \< 60% but only one core run elasticsearch go upto 200%.  
Stast info  
"\_shards": {  
"total": 32,  
"successful": 16,  
"failed": 0  
}

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 31, 2017, 10:18am UTC](https://discuss.elastic.co/t/multiple-core-cpu/113648/4 "2017-12-31T10:18:18Z")

</div>

What indexing and/or query rate do you need to support? Are you throwing enough load at the node to make it require the use of more than 1-2 cores?

---

<div class="post-metadata">

**Author:** ![hoang2117](https://avatars.discourse-cdn.com/v4/letter/h/6de8d8/32.png) [@hoang2117](https://discuss.elastic.co/u/hoang2117)\
**Post date:** [December 31, 2017, 10:25am UTC](https://discuss.elastic.co/t/multiple-core-cpu/113648/5 "2017-12-31T10:25:19Z")

</div>

I will explain our purpose.  
I have 1 main index for product information, and 2 logs indexes. When user request to view product list, i will query for search on elasticsearch and return information, before return info i log request information to elasticsearch.  
On peak time, for example when we send push notification to user, user access to out system, as i imagine, each request will be process by one uwsgi server and on this time it will make 2 request to elastisearch system to search and write logs.  
I have multiple uwsgi (24) process running to handle request, so as current situation only one elasticsearch process is running so it make request slow down because of queuing for elasticsearch. so if we can make it running on more than 1 core it will reduces response time

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [December 31, 2017, 4:33pm UTC](https://discuss.elastic.co/t/multiple-core-cpu/113648/6 "2017-12-31T16:33:34Z")

</div>

What makes you think that Elasticsearch can only use one core?

---

<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:** [January 28, 2018, 4:33pm UTC](https://discuss.elastic.co/t/multiple-core-cpu/113648/7 "2018-01-28T16:33:35Z")

</div>

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