# Optimizing Speed of Searches/Visualizations

**URL:** <https://discuss.elastic.co/t/optimizing-speed-of-searches-visualizations/108164>\
**Category:** Elasticsearch\
**Created:** [November 17, 2017, 4:27pm UTC](https://discuss.elastic.co/t/optimizing-speed-of-searches-visualizations/108164 "2017-11-17T16:27:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CDR](https://avatars.discourse-cdn.com/v4/letter/c/d9b06d/32.png) [@CDR](https://discuss.elastic.co/u/CDR)\
**Post date:** [November 17, 2017, 4:27pm UTC](https://discuss.elastic.co/t/optimizing-speed-of-searches-visualizations/108164/1 "2017-11-17T16:27:12Z")

</div>

In my Elastic Stack we are running Elasticsearch, Logstash and Kibana. The Elasticsearch instance has 171,802,946 log lines in it. The issue that I am running into is that when I try to create a visualization/dashboard all of my queries time out. Is there some way that I can speed up the searches so that they do not time out? Is there some seetings that I need to change?

Thanks!

---

<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:** [November 17, 2017, 4:35pm UTC](https://discuss.elastic.co/t/optimizing-speed-of-searches-visualizations/108164/2 "2017-11-17T16:35:21Z")

</div>

Have you been able to identify what is limiting performance, e.g. CPU, heap, disk I/O? What is the specification of your cluster? How much data do you have in it?

---

<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:** [December 15, 2017, 4:35pm UTC](https://discuss.elastic.co/t/optimizing-speed-of-searches-visualizations/108164/3 "2017-12-15T16:35:40Z")

</div>

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