# Percolator Performance (ES 5.6)

**URL:** <https://discuss.elastic.co/t/percolator-performance-es-5-6/224173>\
**Category:** Elasticsearch\
**Created:** [March 18, 2020, 6:44pm UTC](https://discuss.elastic.co/t/percolator-performance-es-5-6/224173 "2020-03-18T18:44:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dolphorama](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dolphorama/32/64687_2.png) [@dolphorama](https://discuss.elastic.co/u/dolphorama)\
**Post date:** [March 18, 2020, 6:44pm UTC](https://discuss.elastic.co/t/percolator-performance-es-5-6/224173/1 "2020-03-18T18:44:13Z")

</div>

Hi,

Since moving from 2.x to 5.6 we have seen a drastic increase in overall query time, and one the biggest culprits is percolation.

After some research, I've been looking at the `"query.extraction_result" : "failed"` count to see which queries aren't being extracted along with the count.

A couple questions:

Why would this seemingly simple query not be extracted? Is there an API to determine why a given query wouldn't be extracted?

```auto
"query": {
  "bool": {
    "filter": [
      {
        "range": {
          "some_field": {
            "gte": 100
          }
        }
      }
    ]
  }
}

```

Also how many un-extracted queries is too many? I realize this is almost certainly going to be dependent on other factors, but I just want to get sense of if it's worth pulling on this thread.

Is there anything else that could contribute to excessive percolator query times?

Thanks!

---

<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:** [April 15, 2020, 6:44pm UTC](https://discuss.elastic.co/t/percolator-performance-es-5-6/224173/2 "2020-04-15T18:44:15Z")

</div>

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