# Tracing performance issues **URL:** \ **Category:** Elasticsearch\ **Created:** [December 9, 2013, 8:27pm UTC](https://discuss.elastic.co/t/tracing-performance-issues/14777 "2013-12-09T20:27:18Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![courtenay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/courtenay/32/1933_2.png) [@courtenay](https://discuss.elastic.co/u/courtenay)\ **Post date:** [December 9, 2013, 8:27pm UTC](https://discuss.elastic.co/t/tracing-performance-issues/14777/1 "2013-12-09T20:27:18Z")
Hey! _What is your favorite way to closely inspect query performance?_ We recently upgraded from 0.19.2 to 0.90.5, and moved off AWS onto dedicated hardware. The new cluster runs at a much lower load, and is on SSDs. You'd think that performance would increase vastly, but instead it dropped - our queries are now awful, are around 400ms. Is there a way of seeing where the breakdown is? For example, mysql has EXPLAIN... which can indicate index issues. -- Courtenay -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/db27aa7b-7907-4e05-82c9-236992be08d7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/db27aa7b-7907-4e05-82c9-236992be08d7%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 9, 2013, 9:02pm UTC](https://discuss.elastic.co/t/tracing-performance-issues/14777/2 "2013-12-09T21:02:46Z")
You never mentioned what OS, but assuming linux you might want to look at this - [http://dev.nuodb.com/techblog/tuning-linux-io-scheduler-ssds](http://dev.nuodb.com/techblog/tuning-linux-io-scheduler-ssds) Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 10 December 2013 07:27, courtenay [court3nay@gmail.com](mailto:court3nay@gmail.com) wrote: > Hey! > > _What is your favorite way to closely inspect query performance?_ > > We recently upgraded from 0.19.2 to 0.90.5, and moved off AWS onto > dedicated hardware. The new cluster runs at a much lower load, and is on > SSDs. > > You'd think that performance would increase vastly, but instead it dropped > > - our queries are now awful, are around 400ms. Is there a way of seeing > where the breakdown is? For example, mysql has EXPLAIN... which can > indicate index issues. > > -- Courtenay > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/db27aa7b-7907-4e05-82c9-236992be08d7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/db27aa7b-7907-4e05-82c9-236992be08d7%40googlegroups.com) > . > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624aPa-TPA6NuQOuJ2eMWjt9r6HKoEcuqxy5SeRAc5j26vA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624aPa-TPA6NuQOuJ2eMWjt9r6HKoEcuqxy5SeRAc5j26vA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [December 9, 2013, 10:07pm UTC](https://discuss.elastic.co/t/tracing-performance-issues/14777/3 "2013-12-09T22:07:58Z")
Can you give more info about CPU, RAM, OS, JVM? Maybe network? How does your queries look like? You shoud use monitoring tools to watch your query workload and if your resources can deal with it. Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGJiGUGfXxTW9bTYk4KO7F323EFD%2BxLerRR04XLSPH2jQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGJiGUGfXxTW9bTYk4KO7F323EFD%2BxLerRR04XLSPH2jQ%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:02am UTC](https://discuss.elastic.co/t/tracing-performance-issues/14777/4 "2017-07-06T02:02:22Z")