# Seeing degradation of repeated search queries over time

**URL:** <https://discuss.elastic.co/t/seeing-degradation-of-repeated-search-queries-over-time/82456>\
**Category:** Elasticsearch\
**Created:** [April 15, 2017, 12:55am UTC](https://discuss.elastic.co/t/seeing-degradation-of-repeated-search-queries-over-time/82456 "2017-04-15T00:55:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![grishick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grishick/32/17392_2.png) [@grishick](https://discuss.elastic.co/u/grishick)\
**Post date:** [April 15, 2017, 12:55am UTC](https://discuss.elastic.co/t/seeing-degradation-of-repeated-search-queries-over-time/82456/1 "2017-04-15T00:55:02Z")

</div>

We are observing a rather strange behavior. The same query keeps getting slower with every subsequent request without us loading up any new data. After ES server has been running for a couple of days, the speed goes down to 10% of what it was right after reboot.

---

<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:** [April 17, 2017, 5:22am UTC](https://discuss.elastic.co/t/seeing-degradation-of-repeated-search-queries-over-time/82456/2 "2017-04-17T05:22:57Z")

</div>

What version? What JVM? What are your settings?  
What is the query?

There's not much to work with here, so more details would help us help you 🙂

---

<div class="post-metadata">

**Author:** ![grishick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grishick/32/17392_2.png) [@grishick](https://discuss.elastic.co/u/grishick)\
**Post date:** [April 18, 2017, 4:43am UTC](https://discuss.elastic.co/t/seeing-degradation-of-repeated-search-queries-over-time/82456/3 "2017-04-18T04:43:25Z")

</div>

Elastic 5.0.2  
JVM: java-1.8.0-openjdk  
JVM options: -Xmx80g -Xms80g

non-default settings in elasticsearch.yml:

```
script.inline: true
script.engine.groovy.inline.aggs: true
script.engine.groovy.inline.update: true
script.engine.groovy.inline.search: true
action.auto_create_index: true
```

---

<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:** [April 18, 2017, 6:03am UTC](https://discuss.elastic.co/t/seeing-degradation-of-repeated-search-queries-over-time/82456/4 "2017-04-18T06:03:35Z")

</div>

That is a very large heap - much bigger than what we recommend. Do you have monitoring installed so you can look at how heap usage and GC varies over time? Do you see anything around GC reported in the logs?

As you also seem to be using inline Groovy scripts I did a quick search on Github. I found a few issues ([this](https://github.com/elastic/elasticsearch/issues/21854) and [this](https://github.com/elastic/elasticsearch/issues/19396)) around not using scripts with parameters which can cause memory problems as scripts are constantly recompiled. How are you using the inline Groovy scripts?

---

<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:** [May 16, 2017, 6:15am UTC](https://discuss.elastic.co/t/seeing-degradation-of-repeated-search-queries-over-time/82456/5 "2017-05-16T06:15:02Z")

</div>

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