# Term query performance issue with respect to size parameter in search query

**URL:** <https://discuss.elastic.co/t/term-query-performance-issue-with-respect-to-size-parameter-in-search-query/154765>\
**Category:** Elasticsearch\
**Created:** [October 31, 2018, 7:51am UTC](https://discuss.elastic.co/t/term-query-performance-issue-with-respect-to-size-parameter-in-search-query/154765 "2018-10-31T07:51:46Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 31, 2018, 10:12am UTC](https://discuss.elastic.co/t/term-query-performance-issue-with-respect-to-size-parameter-in-search-query/154765/5 "2018-10-31T10:12:51Z")

</div>

> [@Sekhar1](#):
>
> Please guide as soon as possible

This is not needed. Read [this](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and specifically the "Also be patient" part.

> I need to know single node how many maximum requests can I process.

It depends... I'd encourage you looking at Rally project to run your benchmarks.

If you have only one node, then that won't help to change the number of replicas. Note that doing a benchmark with one node if you have in production 10 nodes does not make sense to me. You can't extract any valid number from your test.  
You should test against a similar platform that you will have in production

---

_[View the full topic](https://discuss.elastic.co/t/term-query-performance-issue-with-respect-to-size-parameter-in-search-query/154765)._
