# Percolate Performance **URL:** \ **Category:** Elasticsearch\ **Created:** [October 17, 2012, 7:59pm UTC](https://discuss.elastic.co/t/percolate-performance/9396 "2012-10-17T19:59:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Adam\_Georgiou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adam_georgiou/32/1409_2.png) [@Adam\_Georgiou](https://discuss.elastic.co/u/Adam_Georgiou)\ **Post date:** [October 17, 2012, 7:59pm UTC](https://discuss.elastic.co/t/percolate-performance/9396/1 "2012-10-17T19:59:44Z")
Hey Guys, Another investigative question here -- trying to figure out if elasticsearch is right for a certain project my team is working on: Does anyone have any hard metrics on how the percolate feature holds up against different sized datasets and how it fares with real time query indexing/percolating. I've seen relatively small stuff discussed anecdotally, but am wondering if anyone has any specifics. In our current architecture we have ~500,000 queries stored and percolate (we call it profile) around 10 documents a minute through it, expecting responses in under (or around) half a second. This doesn't seem like it would be too hard of a problem for a properly driven elasticsearch setup, but we also add/remove about 50 queries/minute from our index simultaneously while profiling documents. Would ElasticSearch block in such cases? Wondering... -Adam -- ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [October 19, 2012, 2:56am UTC](https://discuss.elastic.co/t/percolate-performance/9396/2 "2012-10-19T02:56:29Z")
Hi, Depends on the hardware and query complexity... 🙂 ## Otis Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) On Wednesday, October 17, 2012 3:59:44 PM UTC-4, Adam Georgiou wrote: > Hey Guys, > > Another investigative question here -- trying to figure out if > elasticsearch is right for a certain project my team is working on: > > Does anyone have any hard metrics on how the percolate feature holds up > against different sized datasets and how it fares with real time query > indexing/percolating. I've seen relatively small > stuff discussed anecdotally, but am wondering if anyone has any specifics. > > In our current architecture we have ~500,000 queries stored and percolate > (we call it profile) around 10 documents a minute through it, expecting > responses in under (or around) half a second. This doesn't seem like it > would be too hard of a problem for a properly driven elasticsearch setup, > but we also add/remove about 50 queries/minute from our > index simultaneously while profiling documents. Would Elasticsearch block > in such cases? > > Wondering... > > -Adam -- ---
**Author:** ![karmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/karmi/32/44951_2.png) [@karmi](https://discuss.elastic.co/u/karmi)\ **Post date:** [October 19, 2012, 8:00am UTC](https://discuss.elastic.co/t/percolate-performance/9396/3 "2012-10-19T08:00:06Z")
Hi, I think everybody would be interested in a properly executed and repeatable benchmark of that... For what it's worth, in one of my past contracts, we had like ~ 2,500 registered queries, tens of millions of docs, and used percolator for "alert" use cases (every document being indexed was running through percolator, not too high indexing rate though), as well as "document clustering" use case (when exporting, tell me what "topics" this document is about, run every document being exported against multiple percolator queries). It performed very well -- we never noticed any performance issues, it wasn't slowing down the throughput. > Would Elasticsearch block in such cases? Certainly not -- after all, percolator queries are just "special" documents in a "special" index. Karel On Wednesday, October 17, 2012 9:59:44 PM UTC+2, Adam Georgiou wrote: > Hey Guys, > > Another investigative question here -- trying to figure out if > elasticsearch is right for a certain project my team is working on: > > Does anyone have any hard metrics on how the percolate feature holds up > against different sized datasets and how it fares with real time query > indexing/percolating. I've seen relatively small > stuff discussed anecdotally, but am wondering if anyone has any specifics. > > In our current architecture we have ~500,000 queries stored and percolate > (we call it profile) around 10 documents a minute through it, expecting > responses in under (or around) half a second. This doesn't seem like it > would be too hard of a problem for a properly driven elasticsearch setup, > but we also add/remove about 50 queries/minute from our > index simultaneously while profiling documents. Would Elasticsearch block > in such cases? > > Wondering... > > -Adam -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:07am UTC](https://discuss.elastic.co/t/percolate-performance/9396/4 "2017-07-06T03:07:57Z")