# Deleting and creating indexes over time kills index performance **URL:** https://discuss.elastic.co/t/deleting-and-creating-indexes-over-time-kills-index-performance/38737 **Category:** Elasticsearch **Created:** [January 8, 2016, 2:50pm UTC](https://discuss.elastic.co/t/deleting-and-creating-indexes-over-time-kills-index-performance/38737 "2016-01-08T14:50:33Z") **Posts on this page:** 1 **Showing post:** 14
### 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: [January 13, 2016, 10:09pm UTC](https://discuss.elastic.co/t/deleting-and-creating-indexes-over-time-kills-index-performance/38737/14 "2016-01-13T22:09:25Z")
This sure sounds _similar_ to the issue I've been tracking here: > [@CPU usage slowly climbs until ES needs a restart](https://discuss.elastic.co/t/cpu-usage-slowly-climbs-until-es-needs-a-restart/38276): > > Hi everyone, We're seeing kind of an annoying issue with our ES cluster which is that after 7-10 days (this is not a science, it's just whenever the problem becomes bad enough) the CPU ES is using is 2-3x more than after a service restart. Let me put this a slightly other way just for clarity... ES runs fine for a while then all of a sudden we notice CPU usage start climbing even though the load (requests we're sending to ES) is the same. It climbs, and climbs and climbs until the latency of t… Interestingly enough, our daily process is to re-index the same data to a new daily index and then swap aliases... we do so little indexing outside of the nightly index that I couldn't honestly say if we're seeing index slow down but we are definitely seeing query slowdowns because of all the massive CPU ES uses for no reason until we restart all of the nodes (our ES cluster is 99.99% searching). --- _[View the full topic](https://discuss.elastic.co/t/deleting-and-creating-indexes-over-time-kills-index-performance/38737)._