# Performance issues that make no sense **URL:** \ **Category:** Kibana\ **Created:** [May 12, 2017, 3:47pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597 "2017-05-12T15:47:35Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\ **Post date:** [May 12, 2017, 3:47pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/1 "2017-05-12T15:47:35Z")
Hi, I've been working with ES 5.2.2 for the past few months and I can't seem to make searches run fast enough. They even timeout quite a bit. My set up: I have a 1 dedicated Logstash node 3 master eligible ES nodes (8GB available RAM, I set half of it, 4GB, in the JVM file) 1 coordinating node with kibana on it My sharding is 1 primary with 2 replicas. So when I search past 12 hours, I get a timeout which seems ridiculous because I only have about 70k documents at 160mb each day/index so you'd think things would be going fast enough but they aren't. I've done a ton of reading on how to make things faster but nothing seems to work. As a side question, is m\_lockall automatically set in the YAML file in ES 5.X, or I need to explicitly set it? Thanks a bunch!! ---
**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:** [May 12, 2017, 9:08pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/2 "2017-05-12T21:08:33Z")
What type of queries are you running? How much CPU does each node have? What kind of storage do you use? Do you have monitoring installed so you can get some clues from that? ---
**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\ **Post date:** [May 12, 2017, 10:39pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/3 "2017-05-12T22:39:32Z")
A basic search all (\*) query is what I'm referring to, but it's only a few 10k of documents that it's searching through... sadly i don't have monitoring installed and can't install it because I've already used up the trial. These are virtual machines using ssds and about half of the storage is used up by past indexes. Can those past indices have an impact on searches that don't even look at those shards? and I'll have to check on the CPU.. what is a lower limit of the cpus? Does it have that strong of an impact on performace? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [May 13, 2017, 4:01am UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/4 "2017-05-13T04:01:34Z")
Can you show your exact query? Can you try with just: ``` GET _search?size=1 ``` And share here the result? ---
**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\ **Post date:** [May 13, 2017, 8:22pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/5 "2017-05-13T20:22:09Z")
> [@dadoonet](#): > > GET \_search?size=1 {"took":6346,"timed\_out":false,"\_shards":{"total":20,"successful":19,"failed":0},"hits":{"total":5417057,"max\_score":1.0,"hits":[{\ ---
**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\ **Post date:** [May 14, 2017, 5:14pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/6 "2017-05-14T17:14:37Z")
Some more statistics that I found that could be interesting: When now do GET \_search?size=1 I get more or less: > { > "took": 12, > "timed\_out": false, > "\_shards": { > "total": 30, > "successful": 30, > "failed": 0 > } But what I was specifically referring to was the responsiveness of the "Discover" tab. Even just looking at the past 15 minutes the response time is: Query Duration 1861ms Request Duration 2538ms and past 24 hours: Query Duration 22710ms Request Duration 26900ms Hits 78176 I included the hits to show that it is so few ( and that is over one shard and 2 replicas). Any ideas? ---
**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\ **Post date:** [May 16, 2017, 3:50pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/7 "2017-05-16T15:50:47Z")
Anyone have some insight? ---
**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\ **Post date:** [May 17, 2017, 3:38pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/8 "2017-05-17T15:38:07Z")
I guess the bigger question is why would the discover tab be so much slower retrieving a query than the curl command? ---
**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\ **Post date:** [June 8, 2017, 11:08pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/9 "2017-06-08T23:08:11Z")
hello? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 30, 2017, 2:16pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/10 "2017-06-30T14:16:24Z")
Knowing that there is Kibana in the middle, may be Kibana does not have enough memory or something like that? I'm moving your question to #kibana in case my colleagues have any idea. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 28, 2017, 2:16pm UTC](https://discuss.elastic.co/t/performance-issues-that-make-no-sense/85597/11 "2017-07-28T14:16:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.