# Configuration for High Volume Search 10k/sec

**URL:** <https://discuss.elastic.co/t/configuration-for-high-volume-search-10k-sec/98609>\
**Category:** Elasticsearch\
**Created:** [August 28, 2017, 10:16pm UTC](https://discuss.elastic.co/t/configuration-for-high-volume-search-10k-sec/98609 "2017-08-28T22:16:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![wpearson4](https://avatars.discourse-cdn.com/v4/letter/w/cdc98d/32.png) [@wpearson4](https://discuss.elastic.co/u/wpearson4)\
**Post date:** [August 28, 2017, 10:16pm UTC](https://discuss.elastic.co/t/configuration-for-high-volume-search-10k-sec/98609/1 "2017-08-28T22:16:30Z")

</div>

Cluster Id: b3ceb5

I am currently running elastic search in Elastic cloud. I have a single node cluster with 64 gb of ram and 1.5 terabytes of hard drive space. I am doing high volume of searches. Users upload csv files with the search terms, I use Nest to generate lucene queries and submit them in parallel to elastic search server. I noticed at one point I maxed the cpu out at 10k request/second and response time of the node increased significantly, 80 seconds to return a document. What type of configuration would I need to overcome this issue? Is the single node my point of failure?

Thanks in Advance.

---

<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:** [August 29, 2017, 1:54am UTC](https://discuss.elastic.co/t/configuration-for-high-volume-search-10k-sec/98609/2 "2017-08-29T01:54:13Z")

</div>

Yes, a single node is a bad idea because you have no redundancy or load balancing, it'd be a good start.

---

<div class="post-metadata">

**Author:** ![wpearson4](https://avatars.discourse-cdn.com/v4/letter/w/cdc98d/32.png) [@wpearson4](https://discuss.elastic.co/u/wpearson4)\
**Post date:** [August 29, 2017, 3:44pm UTC](https://discuss.elastic.co/t/configuration-for-high-volume-search-10k-sec/98609/3 "2017-08-29T15:44:58Z")

</div>

Thank you for your response. I am looking at moving to the following configuration: 1 Client Node, 1 Master, 2 Data Nodes. My server configuration for each of the data nodes would be 64 gb of ram, 2 TB Hard Drive with 8 cores. The data nodes would also be marked master eligible. My single master node and single client node would each have 8gb ram, 90g hard drive space and 4 cores. I am hoping the configuration will solve my load issues. Does the specifications mentioned seem out of whack?

---

<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:** [August 29, 2017, 10:04pm UTC](https://discuss.elastic.co/t/configuration-for-high-volume-search-10k-sec/98609/4 "2017-08-29T22:04:16Z")

</div>

Elastic Cloud doesn't yet have dedicated node types.  
Are you suggesting moving to a standalone cluster?

---

<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:** [September 26, 2017, 10:04pm UTC](https://discuss.elastic.co/t/configuration-for-high-volume-search-10k-sec/98609/5 "2017-09-26T22:04:40Z")

</div>

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