# Elasticsearch 2.3 poor performance **URL:** \ **Category:** Elasticsearch\ **Created:** [August 5, 2016, 3:13pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-poor-performance/57359 "2016-08-05T15:13:00Z")\ **Posts on this page:** 5\ **Page:** 2
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [August 11, 2016, 7:05pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-poor-performance/57359/21 "2016-08-11T19:05:44Z")
That's sad. So maybe you are not on physical machine? 20 VMs are a huge difference to 20 physical machines. I would re-check software RAID setup. Look for the slowest part of the system first. Also the whole VM setup can be the reason for massive slowdown - e.g. a managed traffic interface to send blocks of VM to host I/O devices. This is suspicious because ES 2+ emits much more IOPS for dealing with translog durability than ES 1+ ---
**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\ **Post date:** [August 12, 2016, 1:48am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-poor-performance/57359/23 "2016-08-12T01:48:31Z")
Can you ask this as a separate question in order to not conflate the topic on this thread please. ---
**Author:** ![1222kkk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/1222kkk/32/23635_2.png) [@1222kkk](https://discuss.elastic.co/u/1222kkk)\ **Post date:** [August 12, 2016, 1:50am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-poor-performance/57359/24 "2016-08-12T01:50:29Z")
I'm sorry, its' my fault. ---
**Author:** ![n.maire](https://avatars.discourse-cdn.com/v4/letter/n/f07891/32.png) [@n.maire](https://discuss.elastic.co/u/n.maire)\ **Post date:** [August 18, 2016, 2:41pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-poor-performance/57359/25 "2016-08-18T14:41:03Z")
Really strange, I've got a much smaller cluster (3 VMs, 4 GB RAM, ES\_HEAP\_SIZE 2GB, virtual disks on SAN, OS Debian 8, Oracle Java 8 update 101, almost all default elasticsearch configuration) and it can easily index 2K docs/sec with an average doc size of about 0.8 KB, so with a cluster like yours you should be able to get much, much higher performance. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:26pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-poor-performance/57359/26 "2017-07-05T22:26:53Z")
[Previous page](https://discuss.elastic.co/t/elasticsearch-2-3-poor-performance/57359.md?page=1)