The config on my nodes is: Running version 5.3.0 of ES,Logstash, and Kibana 8 CPUs 250gig SSD drives They have 40 Gigs of RAM I allocated 16 gigs to the heap 5 ES nodes Index configured for 5 shards, 1 replica avg shard size for the index is about 20 gigs (a little over 20,000,000 docs) avg CPU ut…

I do not see anything obviously wrong with it, but as you are using VMs I would recommend that you verify that Elasticsearch actually has access to the resources you have specified. memory ballooning or overallocation of CPU can have significant negative impact on performance. Each query or aggrega…

I think my heap is sized right but searches are still super slow

Elastic Stack Elasticsearch

red888 (red der) May 1, 2017, 11:30am 7

VMs, usually just 5 to 10 shards. I'm just using the discover pane in kibana.

But with my current config are there any red flags?

Will increasing the number of shards to utilize more CPU and improve performance?

Topic		Replies	Views
Slow search response time (low CPU utilization) Elasticsearch	7	3391	July 31, 2019
Is heapCurrent reflective of performance Elasticsearch	12	1049	June 27, 2017
ES used heap % grows slowly until system becomes unresponsive Elasticsearch	21	5523	July 5, 2017
Elasticsearch querying is terribly slow Elasticsearch	11	20029	May 19, 2017
Elasticsearch 1.5.2 deployment issue Elasticsearch	4	541	July 5, 2017

I think my heap is sized right but searches are still super slow

Related topics