# Non-linear increase in the response time to grow concurrency

**URL:** <https://discuss.elastic.co/t/non-linear-increase-in-the-response-time-to-grow-concurrency/8425>\
**Category:** Elasticsearch\
**Created:** [July 16, 2012, 2:21pm UTC](https://discuss.elastic.co/t/non-linear-increase-in-the-response-time-to-grow-concurrency/8425 "2012-07-16T14:21:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nikolay\_Zhariy](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@Nikolay\_Zhariy](https://discuss.elastic.co/u/Nikolay_Zhariy)\
**Post date:** [July 16, 2012, 2:21pm UTC](https://discuss.elastic.co/t/non-linear-increase-in-the-response-time-to-grow-concurrency/8425/1 "2012-07-16T14:21:37Z")

</div>

We're using VMWare Esxi virtual machines with ElasticSearch 0.19.8 cluster  
and have some troubleshooting to do.

Index size is about 50Mb, Virtual machines RAM 2Gb. Testing via  
ApacheBenchmark tool gives 1-3ms response time with concurrency 1, 10-30ms  
with concurrency 5, 100-300ms with concurrency 10. Concurrency more than 10  
fully crashes the system.

How do we properly configure ElasticSearch to increase concurrencies?

---

<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:** [July 6, 2017, 3:20am UTC](https://discuss.elastic.co/t/non-linear-increase-in-the-response-time-to-grow-concurrency/8425/2 "2017-07-06T03:20:13Z")

</div>