# Is it OK to extend the CPU core to Elasticsearch? **URL:** \ **Category:** Elasticsearch\ **Created:** [January 18, 2017, 4:11pm UTC](https://discuss.elastic.co/t/is-it-ok-to-extend-the-cpu-core-to-elasticsearch/72046 "2017-01-18T16:11:42Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![st1t](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/st1t/32/9188_2.png) [@st1t](https://discuss.elastic.co/u/st1t)\ **Post date:** [January 18, 2017, 4:11pm UTC](https://discuss.elastic.co/t/is-it-ok-to-extend-the-cpu-core-to-elasticsearch/72046/1 "2017-01-18T16:11:42Z")
I am planning to introduce the Elasticsearch server in earnest. We plan to use an on-premises server due to security restrictions. So I thought. How far is the Elasticsearch's CPU processing to load balance nicely? Normally, excessive multicore thinks whether it causes context switch. I also understand the upper limit of JVM's object pointer. How much core do you have on one server? Note: Because I plan to use high-performance SSD, Network thinks I will become a bottleneck before DISK I/O. By the way, as far as the budget permits, considering the hardware performance it has the following structure. CPU: Intel Xeon E5-2698 \* 2 (Total 80 threads) SSD: Intel SSD 750 Memory: 128 GB If the CPU becomes a bottleneck on the contrary, I'm thinking to divide it by KVM, Docker, etc and use it. I am happy to be able to use Elastic Cloud Enterprise as soon as possible 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 15, 2017, 4:12pm UTC](https://discuss.elastic.co/t/is-it-ok-to-extend-the-cpu-core-to-elasticsearch/72046/2 "2017-02-15T16:12:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.