# Percolate performance: 1.7.2 -\> 2.1 Any improvement?
**URL:** https://discuss.elastic.co/t/percolate-performance-1-7-2-2-1-any-improvement/37362
**Category:** Elasticsearch
**Created:** [December 16, 2015, 3:01pm UTC](https://discuss.elastic.co/t/percolate-performance-1-7-2-2-1-any-improvement/37362 "2015-12-16T15:01:18Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Nikolay\_Klimchuk](https://discuss.elastic.co/u/Nikolay_Klimchuk)
#### Post date: [December 16, 2015, 3:01pm UTC](https://discuss.elastic.co/t/percolate-performance-1-7-2-2-1-any-improvement/37362/1 "2015-12-16T15:01:18Z")
We're not happy with percolate performance in ES 1.7.2
Can we expect lower latency in 2.1?
Thanks
---
### Author:  [@mvg](https://discuss.elastic.co/u/mvg)
#### Post date: [December 16, 2015, 3:41pm UTC](https://discuss.elastic.co/t/percolate-performance-1-7-2-2-1-any-improvement/37362/2 "2015-12-16T15:41:17Z")
No. We're working on making the percolator a bit smarter by only evaluating queries that are likely to match:
This isn't going to help now, since it will be available from 3.0.
How are you currently storing your queries? For example you can use percolator query metadata to cut down the number of queries for the percolator to evaluate.
---
### Author:  [@mvg](https://discuss.elastic.co/u/mvg)
#### Post date: [December 16, 2015, 3:42pm UTC](https://discuss.elastic.co/t/percolate-performance-1-7-2-2-1-any-improvement/37362/3 "2015-12-16T15:42:35Z")
oops, forgot to add the PR link: [https://github.com/elastic/elasticsearch/pull/13646](https://github.com/elastic/elasticsearch/pull/13646)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:30pm UTC](https://discuss.elastic.co/t/percolate-performance-1-7-2-2-1-any-improvement/37362/4 "2017-07-05T23:30:32Z")