# Indexing performance degrading over time

**URL:** <https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229>\
**Category:** Elasticsearch\
**Created:** [January 27, 2016, 12:30pm UTC](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229 "2016-01-27T12:30:27Z")\
**Posts on this page:** 1\
**Showing post:** 55

<div class="post-metadata">

**Author:** ![ivank](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ivank/32/7595_2.png) [@ivank](https://discuss.elastic.co/u/ivank)\
**Post date:** [March 31, 2016, 1:29pm UTC](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229/55 "2016-03-31T13:29:54Z")

</div>

Well, we have tried to change GC, here are the results:

- Default GC - worked fine till it has been changed;
- G1 GC without `-XX:+DisableExplicitGC` - no, didn't helped. One of nodes still becomes overloaded with the same symptoms.
- CMS GC (original `elasticsearch.in.sh` without changes) - works perfect, and even throughput is greater, without long GC pauses.

Yeah, you are right with your default configuration. Well done, guys, keep up the good work!

As for G1, may be submit a bug for it? But I don't know how it can be reproduced in code.

---

_[View the full topic](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229)._