# How to reduce respone time of elasticsearch

**URL:** <https://discuss.elastic.co/t/how-to-reduce-respone-time-of-elasticsearch/220283>\
**Category:** Elasticsearch\
**Created:** [February 21, 2020, 2:26am UTC](https://discuss.elastic.co/t/how-to-reduce-respone-time-of-elasticsearch/220283 "2020-02-21T02:26:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nathlee](https://avatars.discourse-cdn.com/v4/letter/n/ac8455/32.png) [@nathlee](https://discuss.elastic.co/u/nathlee)\
**Post date:** [February 21, 2020, 2:26am UTC](https://discuss.elastic.co/t/how-to-reduce-respone-time-of-elasticsearch/220283/1 "2020-02-21T02:26:23Z")

</div>

I use elasticsearch to store event logs per day like this

 ![Screenshot from 2020-02-21 09-14-36 (1)](https://us1.discourse-cdn.com/elastic/original/3X/c/9/c9d9b96a47563810b4f75a6efdba47f77433a96e.jpeg) .  
I use one node with 16gb ram 8core, sometimes the response time of my server is too slow. I know I shouldn't use too many shards but I must save one event in one index for query in the future.  
this code of my node stats  
[https://jsoneditoronline.org/#left=cloud.d90d4bd97bdc45a1bbd9dfbf262f13fd](https://jsoneditoronline.org/#left=cloud.d90d4bd97bdc45a1bbd9dfbf262f13fd)  
Thank you for support \<3

---

<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:** [February 21, 2020, 6:11am UTC](https://discuss.elastic.co/t/how-to-reduce-respone-time-of-elasticsearch/220283/2 "2020-02-21T06:11:28Z")

</div>

> [@nathlee](#):
>
> I must save one event in one index for query in the future

Why would this be the case?

It looks like you have a lot of very small indices and shards, which is very inefficient and likely to cause performance problems. I would recommend consolidating into fewer larger indices, which should improve performance. How many indices do you have?

---

<div class="post-metadata">

**Author:** ![nathlee](https://avatars.discourse-cdn.com/v4/letter/n/ac8455/32.png) [@nathlee](https://discuss.elastic.co/u/nathlee)\
**Post date:** [February 21, 2020, 12:18pm UTC](https://discuss.elastic.co/t/how-to-reduce-respone-time-of-elasticsearch/220283/3 "2020-02-21T12:18:46Z")

</div>

I have 3057 indies (1 shard /1 index), I save events from time to time, one event in one day has 1 index, that easy for me to count events per day and show it to chart (like a funnel) in kibana. So do you have any ideas to solve that problem? Thank you for your answer

---

<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:** [February 21, 2020, 12:26pm UTC](https://discuss.elastic.co/t/how-to-reduce-respone-time-of-elasticsearch/220283/4 "2020-02-21T12:26:50Z")

</div>

That is far too many small indices and shards. If you data covers a long time period and you want time-based indices, switch to yearly indices instead. If your data set is growing slowly you may be better off not using time-based indices.

---

<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:** [March 20, 2020, 12:26pm UTC](https://discuss.elastic.co/t/how-to-reduce-respone-time-of-elasticsearch/220283/5 "2020-03-20T12:26:50Z")

</div>

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