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

<div class="post-metadata">

**Author:** ![Arun\_Agarwal](https://avatars.discourse-cdn.com/v4/letter/a/59ef9b/32.png) [@Arun\_Agarwal](https://discuss.elastic.co/u/Arun_Agarwal)\
**Post date:** [March 6, 2016, 8:16pm UTC](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229/38 "2016-03-06T20:16:03Z")

</div>

Hey i have been seeing the same issue for a while, do you suggest to open a new discussion or can i put in the data i have here  
I see the cpu going to 95+% with hot threads on

66.6% (332.9ms out of 500ms) cpu usage by thread 'elasticsearch[host][search][T#25]'  
10/10 snapshots sharing following 14 elements  
java.lang.ThreadLocal$ThreadLocalMap.expungeStaleEntry(ThreadLocal.java:617)  
java.lang.ThreadLocal$ThreadLocalMap.remove(ThreadLocal.java:499)  
java.lang.ThreadLocal$ThreadLocalMap.access$200(ThreadLocal.java:298)  
java.lang.ThreadLocal.remove(ThreadLocal.java:222)

if i increase the refresh interval from 30s to 60s the cpu seems to come down, but when i revert it back the cpu on the host starts increasing and stays there until i send a  
sudo kill -QUIT {pid}  
and everything comes back to normal

---

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