# 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:** 59

<div class="post-metadata">

### Author: ![travisbell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/travisbell/32/6272_2.png) [@travisbell](https://discuss.elastic.co/u/travisbell)
#### Post date: [April 14, 2016, 1:48pm UTC](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229/59 "2016-04-14T13:48:35Z")

</div>

We made the switch from G1 to CMS on the entire stack and not only has it indeed, solved the run away CPU problem, look at how much more stable the response times have:

 ![](https://us1.discourse-cdn.com/elastic/original/2X/a/acffc2718820012965997b2704332d6b56af5a66.png)

Crazy to see such a difference in the higher percentiles.

Thanks to everyone here who helped figure this out, I can stop complaining about ES now 😃

---

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