# Not stable response time of elastic cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [July 16, 2019, 8:01am UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671 "2019-07-16T08:01:10Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![pa101](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@pa101](https://discuss.elastic.co/u/pa101)\ **Post date:** [July 16, 2019, 8:01am UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671/1 "2019-07-16T08:01:10Z")
60 shards 3 nodes elastic cluster, response time is pretty volatile from 20ms to 300ms, how could I make response time shorter and more stable? ---
**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:** [July 16, 2019, 8:40am UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671/2 "2019-07-16T08:40:51Z")
What are you doing? What is your hardware like? What is running on the machine? ---
**Author:** ![pa101](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@pa101](https://discuss.elastic.co/u/pa101)\ **Post date:** [July 16, 2019, 9:10am UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671/3 "2019-07-16T09:10:52Z")
normal query，hardware is 8core 16G 3nodes， machine is only running es as a search engine. ---
**Author:** ![pa101](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@pa101](https://discuss.elastic.co/u/pa101)\ **Post date:** [July 16, 2019, 9:12am UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671/4 "2019-07-16T09:12:40Z")
es stores many questions and answers, input a queston, and search for a similar question ---
**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:** [July 16, 2019, 10:13am UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671/5 "2019-07-16T10:13:31Z")
> [@pa101](#): > > normal query Like the following? ```auto GET /index/_search ``` Or a bit more complex than a `match_all`? SSD drives? Or spinning disks? What is the output of: ```auto GET / GET /_cat/nodes?v GET /_cat/health?v GET /_cat/indices?v ``` What is the typical response (the full one please) of a "slow query"? And what was the request? Also have a look at [this great blog post about Slow Queries](https://www.elastic.co/blog/advanced-tuning-finding-and-fixing-slow-elasticsearch-queries). That might help. ---
**Author:** ![pa101](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@pa101](https://discuss.elastic.co/u/pa101)\ **Post date:** [July 16, 2019, 12:01pm UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671/6 "2019-07-16T12:01:33Z")
curl -X GET "[http://localhost:8080/\_cat/nodes?v](http://localhost:8080/_cat/nodes?v)" ```auto ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name 10.30.252.56 28 40 8 1.99 3.28 3.72 mdi - node-56 10.30.252.55 51 55 17 4.91 6.51 7.49 mdi * node-55 10.30.252.54 51 54 16 4.08 6.71 7.40 mdi - node-54 ``` curl -X GET "[http://localhost:8080/\_cat/health?v](http://localhost:8080/_cat/health?v)" ```auto epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent 1563276185 19:23:05 es yellow 3 3 750 250 0 0 10 0 - 98.7% ``` curl -X GET "[http://localhost:8080/\_cat/indices?v](http://localhost:8080/_cat/indices?v)" ```auto health status index uuid pri rep docs.count docs.deleted store.size pri.store.size green open all_with_routing_36_0 -eZAYbBcRqKa6WnjTItJLg 60 2 210232 0 561.2mb 187mb green open all_36_1 tsVykN1GQYe7tScV93ZA0A 60 2 473 0 4.1mb 1.3mb green open all_36_0 F_1uZJ02SzKScZw9wQQMIw 60 2 210232 0 734.3mb 244.7mb yellow open tritalkdoctest0627 cDH2mEicQNGuVkJ-prgxjg 5 3 119 0 1.1mb 390kb yellow open tritalkdoctest0715 QgUYx6BKTvCdIJc1TiOQqg 5 3 119 0 1.1mb 393.6kb green open all_126_1 tHkz0rr-SO2EMKPp8ffL8g 60 2 677 0 4.9mb 1.6mb ``` curl -X GET "[http://localhost:8080/](http://localhost:8080/)" ```auto { "name" : "node-54", "cluster_name" : "es", "cluster_uuid" : "5pxKPv4dTsajsfYabzx_2Q", "version" : { "number" : "6.3.0", "build_flavor" : "default", "build_type" : "tar", "build_hash" : "424e937", "build_date" : "2018-06-11T23:38:03.357887Z", "build_snapshot" : false, "lucene_version" : "7.3.1", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You Know, for Search" } ``` ---
**Author:** ![pa101](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@pa101](https://discuss.elastic.co/u/pa101)\ **Post date:** [July 16, 2019, 12:02pm UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671/7 "2019-07-16T12:02:45Z")
spinning disk, query like GET /index/\_search ---
**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:** [July 16, 2019, 2:49pm UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671/8 "2019-07-16T14:49:16Z")
60 shards is too much IMO. 1 shard is enough here. > spinning disk Switch to SSD drives. Also pasting again one of my questions: > What is the typical response (the full one please) of a "slow query"? And what was the request? Please [read this](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) about how to format. Also note that "6.3.0" has been built more than a year ago. Lot of improvements have been done in the meantime. Could you upgrade to 7.2.0? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 13, 2019, 2:49pm UTC](https://discuss.elastic.co/t/not-stable-response-time-of-elastic-cluster/190671/9 "2019-08-13T14:49:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.