# Bad performance retrive logs

**URL:** <https://discuss.elastic.co/t/bad-performance-retrive-logs/107014>\
**Category:** Kibana\
**Created:** [November 9, 2017, 10:07am UTC](https://discuss.elastic.co/t/bad-performance-retrive-logs/107014 "2017-11-09T10:07:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Giorgio\_Cerruti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/giorgio_cerruti/32/24014_2.png) [@Giorgio\_Cerruti](https://discuss.elastic.co/u/Giorgio_Cerruti)\
**Post date:** [November 9, 2017, 10:07am UTC](https://discuss.elastic.co/t/bad-performance-retrive-logs/107014/1 "2017-11-09T10:07:13Z")

</div>

Hi there,  
I installed my own ELK stack following the docker documentation guideline, now we have a container with ELK installed into it. We've 237,524 logs saved into elasticserch already. For put those messages, I've made a simple node.js script which read from mongodb some documents and push it into elasticsearch directly - no logstash usage.  
Log messages have a filed _type_. So type is our index and his value is the type.  
Now, what we're experiencing is that a very bad performance to retrieve logs searching in the discover section, it can take about 15 seconds to shows all results.  
The issue seems related to the frontend and not to the backend, in fact, I tried also to make some query using curl and the same resultset of data come up in less than 1 second. We increased the discover:sampleSize property up to 10000 this because we would use ELK in development environment also and sometimes we need to retrieve a large dataset of logs for our investigation. My question is that what I can do to increase that performance? Aside to reduce the discover:sampleSize of course. If you need some other information about my configuration please ask me.

Thanks in advance,

Giorgio

---

<div class="post-metadata">

**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\
**Post date:** [November 9, 2017, 10:53pm UTC](https://discuss.elastic.co/t/bad-performance-retrive-logs/107014/2 "2017-11-09T22:53:47Z")

</div>

Hi Giorgio, unfortunately the performance limitation of Discover's document table is a known issue. We're tracking the problem at [https://github.com/elastic/kibana/issues/12665](https://github.com/elastic/kibana/issues/12665). Please subscribe to the issue to be notified of progress, or feel free to submit a PR with any improvements.

Thanks,  
CJ

---

<div class="post-metadata">

**Author:** ![Giorgio\_Cerruti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/giorgio_cerruti/32/24014_2.png) [@Giorgio\_Cerruti](https://discuss.elastic.co/u/Giorgio_Cerruti)\
**Post date:** [November 10, 2017, 7:19am UTC](https://discuss.elastic.co/t/bad-performance-retrive-logs/107014/3 "2017-11-10T07:19:52Z")

</div>

Hi, thank you for the feedback. I'll follow the github sicussion.

Thanks,  
Giorgio

---

<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 8, 2017, 7:20am UTC](https://discuss.elastic.co/t/bad-performance-retrive-logs/107014/4 "2017-12-08T07:20:12Z")

</div>

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