# Big amount of search operations for use in percolator

**URL:** <https://discuss.elastic.co/t/big-amount-of-search-operations-for-use-in-percolator/274786>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [June 2, 2021, 5:23pm UTC](https://discuss.elastic.co/t/big-amount-of-search-operations-for-use-in-percolator/274786 "2021-06-02T17:23:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sanoj85](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sanoj85/32/89731_2.png) [@sanoj85](https://discuss.elastic.co/u/sanoj85)\
**Post date:** [June 2, 2021, 5:23pm UTC](https://discuss.elastic.co/t/big-amount-of-search-operations-for-use-in-percolator/274786/1 "2021-06-02T17:23:41Z")

</div>

Hi,

We are running an index with a field type percolator, which will take a big amount of incoming searches containing documents. I have seen the example ([rally-tracks/default.json at master · elastic/rally-tracks · GitHub](https://github.com/elastic/rally-tracks/blob/master/percolator/operations/default.json)), but this keeps each search as a separate operation.

What I want to be doing is having a large amount of test data in the form of searches (not the contents of the index). Is this possible? Is it even a good idea to begin with?

---

<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:** [June 30, 2021, 5:24pm UTC](https://discuss.elastic.co/t/big-amount-of-search-operations-for-use-in-percolator/274786/2 "2021-06-30T17:24:19Z")

</div>

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