# How many queries per second my server can handle?

**URL:** <https://discuss.elastic.co/t/how-many-queries-per-second-my-server-can-handle/150477>\
**Category:** Elasticsearch\
**Created:** [September 30, 2018, 12:48pm UTC](https://discuss.elastic.co/t/how-many-queries-per-second-my-server-can-handle/150477 "2018-09-30T12:48:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shrimp-Fried-Rice](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shrimp-fried-rice/32/33360_2.png) [@Shrimp-Fried-Rice](https://discuss.elastic.co/u/Shrimp-Fried-Rice)\
**Post date:** [September 30, 2018, 12:48pm UTC](https://discuss.elastic.co/t/how-many-queries-per-second-my-server-can-handle/150477/1 "2018-09-30T12:48:41Z")

</div>

hi, i have dedicated server with 128 gigs of RAM, acting as a single node cluster  
Dual Intel® Xeon® E5-2620 V1 & 2 × 4TB HDD

server is being used for nginx,php,mysql and elasticsearch  
java heap memory is set to 15 GB  
main index is only one  
kibana shows:  
documents count 4.6mil  
data 1.9 GB

current search rate 339.34 /s

i would like to know when should i add more nodes , right now set up is single node cluster.

how many queries per second my current setup can handle ?

Thanks for your time.

---

<div class="post-metadata">

**Author:** ![popa](https://avatars.discourse-cdn.com/v4/letter/p/dec6dc/32.png) [@popa](https://discuss.elastic.co/u/popa)\
**Post date:** [October 1, 2018, 2:01am UTC](https://discuss.elastic.co/t/how-many-queries-per-second-my-server-can-handle/150477/2 "2018-10-01T02:01:03Z")

</div>

Typically each node in an Elastic Stack should be dedicated and contain no additional applications. You'll get better performance if you separate the resources into multiple VMs. Since you have 128 GB of RAM, I would use something like this:

- Elasticsearch (8 GB RAM)
- Elasticsearch (8 GB RAM)
- Elasticsearch (8 GB RAM)
- Logstash (8 GB RAM)
- KIbana / Nginx (4 GB RAM)

There's a limit on how much RAM you should allocate to JVM heap (which is 32GB) due to ordinary object pointers (OOP). Anything below 32GB on a 64-bit system is okay, and will allow Java to used compressed OOPs. If you cross that threshold it will use OOP, and be significantly less effective and you'll just be wasting memory, reducing CPU performance, among other things.

To test and scale your Elastic Stack, I would closely monitor the CPU / RAM / JVM performance. If JVM is consistently using more than 75% of its allocated memory, you might want to upgrade.

Here's a tool that can be used to run some benchmarks: [https://www.elastic.co/blog/rally-1-0-0-released-benchmark-elasticsearch-like-we-do](https://www.elastic.co/blog/rally-1-0-0-released-benchmark-elasticsearch-like-we-do)

---

<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:** [October 29, 2018, 2:14am UTC](https://discuss.elastic.co/t/how-many-queries-per-second-my-server-can-handle/150477/3 "2018-10-29T02:14:22Z")

</div>

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