# ElasticSearch 2.3.0 Performance

**URL:** <https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970>\
**Category:** Elasticsearch\
**Created:** [January 27, 2017, 4:04am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970 "2017-01-27T04:04:52Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mahiz10](https://avatars.discourse-cdn.com/v4/letter/m/a4c791/32.png) [@Mahiz10](https://discuss.elastic.co/u/Mahiz10)\
**Post date:** [January 27, 2017, 4:04am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970/1 "2017-01-27T04:04:52Z")

</div>

I am using elastic search 2.3.0 hosted on AWS Cloud.

I have recently made code changes for using the bulk indexing option provided by elastic.

When i have tested this change on my PERF env , i was happy with the performance achieved.  
But , when i pushed this code to PROD env , the performance was very poor compared to the performance observed in PERF environment.

- Both PERF and PROD environments have the same hardware configuration (m4.2xlarge EC2 Server)
- Data Volume in PERF is about 170 Million Docs Stored in a single index , whereas data volume in PROD is about 800 Million Docs Stored in a single index.

Rest all the configurations in elasticsearch.yml are same in both PERF and PROD environments

I am unable to figure out the poor performance. Please provide me with some pointers.

Thanks

---

<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:** [January 29, 2017, 4:21am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970/2 "2017-01-29T04:21:18Z")

</div>

Are you running the AWS ES service?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 29, 2017, 7:43am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970/3 "2017-01-29T07:43:42Z")

</div>

The main difference seems to be the amount of data in each cluster. As you have a single index, are you assigning your own document IDs and/or performing document updates? Does the shard size differ between the environments?

---

<div class="post-metadata">

**Author:** ![Mahiz10](https://avatars.discourse-cdn.com/v4/letter/m/a4c791/32.png) [@Mahiz10](https://discuss.elastic.co/u/Mahiz10)\
**Post date:** [January 30, 2017, 2:36am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970/4 "2017-01-30T02:36:13Z")

</div>

Shard size is same in both the environments. We are assigning our own document id in both the environments ..

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 30, 2017, 6:18am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970/5 "2017-01-30T06:18:42Z")

</div>

If the shard size is the same, does that mean that you have 4-5 times more shards in the production environment as the number of documents is considerable larger? How many shards do you have? What is the average shard size?

---

<div class="post-metadata">

**Author:** ![Mahiz10](https://avatars.discourse-cdn.com/v4/letter/m/a4c791/32.png) [@Mahiz10](https://discuss.elastic.co/u/Mahiz10)\
**Post date:** [January 31, 2017, 3:57pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970/6 "2017-01-31T15:57:29Z")

</div>

I meant to say number of shards are same.

Both in PERF and PROD , we have 50 Shards for the index.

In Production each shard size is now currently at 6 GB.

I found this out using the command GET /\_cat/shards?v

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 31, 2017, 7:18pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970/7 "2017-01-31T19:18:03Z")

</div>

When you say that performance is poor, are you referring to indexing and/or query performance? What performance are you seeing?

---

<div class="post-metadata">

**Author:** ![Mahiz10](https://avatars.discourse-cdn.com/v4/letter/m/a4c791/32.png) [@Mahiz10](https://discuss.elastic.co/u/Mahiz10)\
**Post date:** [February 1, 2017, 6:47pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970/8 "2017-02-01T18:47:14Z")

</div>

Both Indexing and Querying as well.

Actually Querying is good on PROD as well , when there is no Indexing happening.

When there is indexing running in parallel , querying is slow in response.

---

<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:** [March 1, 2017, 6:47pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-0-performance/72970/9 "2017-03-01T18:47:34Z")

</div>

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