# Settings for improve latency in multithreading requests **URL:** \ **Category:** Elasticsearch\ **Created:** [April 22, 2013, 2:01pm UTC](https://discuss.elastic.co/t/settings-for-improve-latency-in-multithreading-requests/11656 "2013-04-22T14:01:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![vovik911](https://avatars.discourse-cdn.com/v4/letter/v/8baadc/32.png) [@vovik911](https://discuss.elastic.co/u/vovik911)\ **Post date:** [April 22, 2013, 2:01pm UTC](https://discuss.elastic.co/t/settings-for-improve-latency-in-multithreading-requests/11656/1 "2013-04-22T14:01:55Z")
Hi, I'm doing some performance test for future use ES in server application I'm start ES with stock settings (one additional only - index.store.type: memory). I have 2 indexes (in feature will be 25) with 5 shards in each. Each index have two types of documents. First type contains 20-120 documents and updates every 3s, second type contains 1500-3200 documents and updates every 10min. Each document have Average document size - 12kb. I use ES for store and search documents. ES starts in AWS c1.xlarge instance 8cores, 7GB RAM. I use ApacheBenchmark to test performance. I noticed that with increasing concurrency latency is rising. Example GET [http://ec2-XXX-XXX-XXX-XX.eu-west-1.compute.amazonaws.com:9200/index\_name/type/\_search?q=parameter.id:1](http://ec2-XXX-XXX-XXX-XX.eu-west-1.compute.amazonaws.com:9200/index_name/type/_search?q=parameter.id:1) or similar POST request Measurement results of one response latency response size: 729b 1000 requests in 1 thread - 5ms 1000 requests in 100 threads - 53ms response size: 573kb 1000 requests in 1 thread - 24ms 1000 requests in 100 threads - 5520ms What I can tune to improve latency. Sorry for my English. Thanks! ---
**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, 2:40am UTC](https://discuss.elastic.co/t/settings-for-improve-latency-in-multithreading-requests/11656/2 "2017-07-06T02:40:11Z")