# Elasticsearch Query performance while continuous ingestion

**URL:** <https://discuss.elastic.co/t/elasticsearch-query-performance-while-continuous-ingestion/190900>\
**Category:** Elasticsearch\
**Created:** [July 17, 2019, 7:23am UTC](https://discuss.elastic.co/t/elasticsearch-query-performance-while-continuous-ingestion/190900 "2019-07-17T07:23:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jayabal\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jayabal_k/32/41905_2.png) [@Jayabal\_K](https://discuss.elastic.co/u/Jayabal_K)\
**Post date:** [July 17, 2019, 7:23am UTC](https://discuss.elastic.co/t/elasticsearch-query-performance-while-continuous-ingestion/190900/1 "2019-07-17T07:23:01Z")

</div>

At starting Elastic-search query performance is good, but it goes down while continuously ingesting data. when we query elastic-search and ingest data in parallel , query latency is high and performance is low.

Please advise, how to get good performance while doing query and document indexing in parallel?

---

<div class="post-metadata">

**Author:** ![Jayabal\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jayabal_k/32/41905_2.png) [@Jayabal\_K](https://discuss.elastic.co/u/Jayabal_K)\
**Post date:** [July 18, 2019, 8:42am UTC](https://discuss.elastic.co/t/elasticsearch-query-performance-while-continuous-ingestion/190900/2 "2019-07-18T08:42:05Z")

</div>

Any suggestion?

---

<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:** [July 18, 2019, 8:55am UTC](https://discuss.elastic.co/t/elasticsearch-query-performance-while-continuous-ingestion/190900/3 "2019-07-18T08:55:00Z")

</div>

You need to size the cluster based on the combined workload. It sounds like your cluster may not be sized correctly.

---

<div class="post-metadata">

**Author:** ![Jayabal\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jayabal_k/32/41905_2.png) [@Jayabal\_K](https://discuss.elastic.co/u/Jayabal_K)\
**Post date:** [July 18, 2019, 9:03am UTC](https://discuss.elastic.co/t/elasticsearch-query-performance-while-continuous-ingestion/190900/4 "2019-07-18T09:03:17Z")

</div>

Currently I have a cluster of 1 master, 5 datanode, 1 ingest nodes. I have allocated 1.3 vcpu, 3.5Gb memory for all nodes. Indexing rate could be nearly 50-100 docs per second. This is very low indexing rate but the query takes times for this low request too.

Do need more resources for this kind of traffic?  
Please advise.

---

<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:** [July 18, 2019, 10:11am UTC](https://discuss.elastic.co/t/elasticsearch-query-performance-while-continuous-ingestion/190900/5 "2019-07-18T10:11:33Z")

</div>

I would recommend you monitor resource usage and increase resources where needed.

---

<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:** [August 15, 2019, 10:11am UTC](https://discuss.elastic.co/t/elasticsearch-query-performance-while-continuous-ingestion/190900/6 "2019-08-15T10:11:34Z")

</div>

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