# Elastic search 1000 req/s with max response time under 100 ms

**URL:** <https://discuss.elastic.co/t/elastic-search-1000-req-s-with-max-response-time-under-100-ms/376506>\
**Category:** Elasticsearch\
**Created:** [March 27, 2025, 10:33pm UTC](https://discuss.elastic.co/t/elastic-search-1000-req-s-with-max-response-time-under-100-ms/376506 "2025-03-27T22:33:35Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Majri\_Mohamed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majri_mohamed/32/142296_2.png) [@Majri\_Mohamed](https://discuss.elastic.co/u/Majri_Mohamed)\
**Post date:** [March 27, 2025, 10:33pm UTC](https://discuss.elastic.co/t/elastic-search-1000-req-s-with-max-response-time-under-100-ms/376506/1 "2025-03-27T22:33:35Z")

</div>

my server is 85 vCPU with 200 gb ram  
i want to run 1000 req/s of medium search queries and aggregations with 100% success and max latency and response time under 100 ms  
I need help on the configuration please for Elasticsearch the db is about 11 gb

---

<div class="post-metadata">

**Author:** ![Majri\_Mohamed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majri_mohamed/32/142296_2.png) [@Majri\_Mohamed](https://discuss.elastic.co/u/Majri_Mohamed)\
**Post date:** [March 27, 2025, 10:46pm UTC](https://discuss.elastic.co/t/elastic-search-1000-req-s-with-max-response-time-under-100-ms/376506/2 "2025-03-27T22:46:44Z")

</div>

only one index with 20 million records each one under 10 kb

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [March 27, 2025, 11:14pm UTC](https://discuss.elastic.co/t/elastic-search-1000-req-s-with-max-response-time-under-100-ms/376506/3 "2025-03-27T23:14:58Z")

</div>

What did you try so far? And what were your results.

Your entire 11G dataset fits (easily) in 200gb of RAM.

But I’ve no idea what a medium search query mean, is that line a medium steak?

”… and aggregations” is also very imprecise.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 28, 2025, 4:30am UTC](https://discuss.elastic.co/t/elastic-search-1000-req-s-with-max-response-time-under-100-ms/376506/4 "2025-03-28T04:30:38Z")

</div>

Your data is small enough to fit into a single primary shard as well as the page cache, which is good for the type of traffic volumes you describe.

I do have some further questions though.

Which version of Elasticsearch are you using?

Does you index have only a single primary shard?

How frequently do you update the data in the index?

What does your queries and mappings look like?

What latency do you see if you just send a single query at a time?

---

<div class="post-metadata">

**Author:** ![Majri\_Mohamed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majri_mohamed/32/142296_2.png) [@Majri\_Mohamed](https://discuss.elastic.co/u/Majri_Mohamed)\
**Post date:** [April 2, 2025, 1:28pm UTC](https://discuss.elastic.co/t/elastic-search-1000-req-s-with-max-response-time-under-100-ms/376506/5 "2025-04-02T13:28:42Z")

</div>

product example  
{  
"mongo\_id": "671ccb8efa83bca45c9a6f74",  
"id": "17258781",  
"catalog\_number": "MBS136332-1mg",  
"supplier\_catalog\_number": "MBS136332",  
"name": "Chicken Anti Rat Cotton IgG Polyclonal Affinity Purified HRP Labeled",  
"size": "1mg",  
"cluster\_name": "purified-affinity-rabbit",  
"supplier\_id": "544",  
"supplier\_name": "MyBiosource",  
"new\_supplier\_id": "544",  
"new\_supplier\_name": "MyBiosource",  
"buy\_price": 0,  
"sell\_price": 0,  
"price\_valid\_until\_date": null,  
"currency": "EUR",  
"dry\_ice": false,  
"promotion\_price": 0,  
"filters": [  
"Species:Rat",  
"Host:Chicken",  
"Isotype:IgG",  
"Technique:Affinity",  
"Technique:Polyclonal",  
"Technique:Purified",  
"Label:HRP"  
]  
}

20 million records  
3 shards 1 replica  
elastic 8.12.0

my current config  
3 masters , 3 data, 3 coord

query example

{  
"query": {  
"bool": {  
"filter": [  
{ "term": { "name": "anti" } },  
{ "term": { "filters": "Host:Chicken" } }  
]  
}  
},  
"size": 100,  
"track\_total\_hits": false,  
"aggs": { // Add this section back  
"filters\_count": {  
"terms": {  
"field": "filters",  
"size": 250, // Reduced from 100 for better performance  
"order": { "\_count": "desc" } // More useful than ascending keys  
}  
}  
}  
}

---

<div class="post-metadata">

**Author:** ![Majri\_Mohamed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majri_mohamed/32/142296_2.png) [@Majri\_Mohamed](https://discuss.elastic.co/u/Majri_Mohamed)\
**Post date:** [April 2, 2025, 1:30pm UTC](https://discuss.elastic.co/t/elastic-search-1000-req-s-with-max-response-time-under-100-ms/376506/6 "2025-04-02T13:30:29Z")

</div>

product example  
{  
"mongo\_id": "671ccb8efa83bca45c9a6f74",  
"id": "17258781",  
"catalog\_number": "MBS136332-1mg",  
"supplier\_catalog\_number": "MBS136332",  
"name": "Chicken Anti Rat Cotton IgG Polyclonal Affinity Purified HRP Labeled",  
"size": "1mg",  
"cluster\_name": "purified-affinity-rabbit",  
"supplier\_id": "544",  
"supplier\_name": "MyBiosource",  
"new\_supplier\_id": "544",  
"new\_supplier\_name": "MyBiosource",  
"buy\_price": 0,  
"sell\_price": 0,  
"price\_valid\_until\_date": null,  
"currency": "EUR",  
"dry\_ice": false,  
"promotion\_price": 0,  
"filters": [  
"Species:Rat",  
"Host:Chicken",  
"Isotype:IgG",  
"Technique:Affinity",  
"Technique:Polyclonal",  
"Technique:Purified",  
"Label:HRP"  
]  
}

20 million records  
3 shards 1 replica  
elastic 8.12.0

my current config  
3 masters , 3 data, 3 coord

query example

{  
"query": {  
"bool": {  
"filter": [  
{ "term": { "name": "anti" } },  
{ "term": { "filters": "Host:Chicken" } }  
]  
}  
},  
"size": 100,  
"track\_total\_hits": false,  
"aggs": { // Add this section back  
"filters\_count": {  
"terms": {  
"field": "filters",  
"size": 250, // Reduced from 100 for better performance  
"order": { "\_count": "desc" } // More useful than ascending keys  
}  
}  
}  
}
