# Performance/Slowness issues with ES **URL:** \ **Category:** Elasticsearch\ **Created:** [December 31, 2014, 8:25pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444 "2014-12-31T20:25:37Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [December 31, 2014, 8:25pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/1 "2014-12-31T20:25:37Z")
Hey guys, I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - Here is the situation - I am currently running everything on single node - which I know is biggest problem n bottleneck. VM on which I am running is - 24gb ram- 8proc - 2TB storage space Here is snapshot of what I have on ES 12GB heap(used only 50% of what is available) 50 indices 370 shards 185 unassigned 757051595 docs 183.71GB is total space occupied (this is of last 7 days of data only) Now when I am running loading these data on my kibana dashboard, its running very slow. I agree that I need to split the data across multiple nodes - which is like 3 to 5 data node, 1 client node, 1 master node - so even with that configuration - it should run fine I guess may be for 10 to 15 days of data since data would be distributed across multiple data nodes (Again this is my assumption that it will go smooth) - so would this be sufficient or I should also tweak few other config params too - with which I will see some good performance and improvement? I know I am seriously not tweaking some of the important config which I should be but being little new to this world - I am still researching further on this. Should I move to some newer version of ES may be 1.3x or 1.4x which is compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the moment)? - Thanks, Bhumir -- 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/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [January 1, 2015, 3:14am UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/2 "2015-01-01T03:14:18Z")
You're probably at the limits of a single node. You should upgrade to a later version of ES as there is always performance improvements or add more heap or nodes. The default settings of ES are more than suitable up to tens of nodes, you shouldn't need to change anything there in the immediate term and you will definitely see performance improvements. Given you're currently only using one node, you can also disable replicas, that will eliminate those unassigned shards and you can easily add them later. On 1 January 2015 at 07:25, Bhumir Jhaveri [bhumir81@gmail.com](mailto:bhumir81@gmail.com) wrote: > Hey guys, > > I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - Here is > the situation - I am currently running everything on single node - which I > know is biggest problem n bottleneck. > VM on which I am running is - 24gb ram- 8proc - 2TB storage space > Here is snapshot of what I have on ES > 12GB heap(used only 50% of what is available) > 50 indices > 370 shards > 185 unassigned > 757051595 docs > 183.71GB is total space occupied (this is of last 7 days of data only) > > Now when I am running loading these data on my kibana dashboard, its > running very slow. > I agree that I need to split the data across multiple nodes - which is > like 3 to 5 data node, 1 client node, 1 master node - so even with that > configuration - it should run fine I guess may be for 10 to 15 days of data > since data would be distributed across multiple data nodes (Again this is > my assumption that it will go smooth) - > so would this be sufficient or I should also tweak few other config params > too - with which I will see some good performance and improvement? > > I know I am seriously not tweaking some of the important config which I > should be but being little new to this world - I am still researching > further on this. > > Should I move to some newer version of ES may be 1.3x or 1.4x which is > compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the > moment)? > > - Thanks, > Bhumir > > -- > 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/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAEYi1X8CvovwGwcZ5dN9onJhnR8b4xp9ox%3DgKOg479OH6Mq1tA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8CvovwGwcZ5dN9onJhnR8b4xp9ox%3DgKOg479OH6Mq1tA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Arie](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Arie](https://discuss.elastic.co/u/Arie)\ **Post date:** [January 1, 2015, 7:18pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/3 "2015-01-01T19:18:03Z")
Hi How are your queries build up. In a default situation Kibana queries all indices, it can help to query only the indices that you need. Beside that there is a dashboard option (preload fields) to improve your query when it concerns a lot of data tot query every time you refresh your panels. hth,, Arie. Op woensdag 31 december 2014 21:25:37 UTC+1 schreef Bhumir Jhaveri: > Hey guys, > > I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - Here is > the situation - I am currently running everything on single node - which I > know is biggest problem n bottleneck. > VM on which I am running is - 24gb ram- 8proc - 2TB storage space > Here is snapshot of what I have on ES > 12GB heap(used only 50% of what is available) > 50 indices > 370 shards > 185 unassigned > 757051595 docs > 183.71GB is total space occupied (this is of last 7 days of data only) > > Now when I am running loading these data on my kibana dashboard, its > running very slow. > I agree that I need to split the data across multiple nodes - which is > like 3 to 5 data node, 1 client node, 1 master node - so even with that > configuration - it should run fine I guess may be for 10 to 15 days of data > since data would be distributed across multiple data nodes (Again this is > my assumption that it will go smooth) - > so would this be sufficient or I should also tweak few other config params > too - with which I will see some good performance and improvement? > > I know I am seriously not tweaking some of the important config which I > should be but being little new to this world - I am still researching > further on this. > > Should I move to some newer version of ES may be 1.3x or 1.4x which is > compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the > moment)? > > - Thanks, > Bhumir -- 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/4894dbd3-625f-4901-a0b2-7e06775060b1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4894dbd3-625f-4901-a0b2-7e06775060b1%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 2, 2015, 4:14pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/4 "2015-01-02T16:14:02Z")
I have plan to upgrade this to ES1.4x but just need to make sure that version upgrade is smooth and free of any issues - I already have around 300gigs of data so hope that ES1.4 would give me better performance. On Wednesday, December 31, 2014 7:14:46 PM UTC-8, Mark Walkom wrote: > You're probably at the limits of a single node. You should upgrade to a > later version of ES as there is always performance improvements or add more > heap or nodes. The default settings of ES are more than suitable up to tens > of nodes, you shouldn't need to change anything there in the immediate term > and you will definitely see performance improvements. > > Given you're currently only using one node, you can also disable replicas, > that will eliminate those unassigned shards and you can easily add them > later. > > On 1 January 2015 at 07:25, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) > \\> wrote: > > > Hey guys, > > > > I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - Here > > is the situation - I am currently running everything on single node - which > > I know is biggest problem n bottleneck. > > VM on which I am running is - 24gb ram- 8proc - 2TB storage space > > Here is snapshot of what I have on ES > > 12GB heap(used only 50% of what is available) > > 50 indices > > 370 shards > > 185 unassigned > > 757051595 docs > > 183.71GB is total space occupied (this is of last 7 days of data only) > > > > Now when I am running loading these data on my kibana dashboard, its > > running very slow. > > I agree that I need to split the data across multiple nodes - which is > > like 3 to 5 data node, 1 client node, 1 master node - so even with that > > configuration - it should run fine I guess may be for 10 to 15 days of data > > since data would be distributed across multiple data nodes (Again this is > > my assumption that it will go smooth) - > > so would this be sufficient or I should also tweak few other config > > params too - with which I will see some good performance and improvement? > > > > I know I am seriously not tweaking some of the important config which I > > should be but being little new to this world - I am still researching > > further on this. > > > > Should I move to some newer version of ES may be 1.3x or 1.4x which is > > compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the > > moment)? > > > > - Thanks, > > Bhumir > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f5089f20-54ef-4a05-b363-82e8408300ae%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/06054b58-a3f9-412e-a564-9e2c10f1300c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/06054b58-a3f9-412e-a564-9e2c10f1300c%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 2, 2015, 4:18pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/5 "2015-01-02T16:18:58Z")
Hey, No it queries only the those set of groups which I require on dashboard - I am not using \_all - but having done that it is still huge set of data which I am using here to generate the dashboard. One problem which I noticed is like the documents which are there consists of 14 columns - as in I am storing data for 14 different fields in one single document - and by default ES puts indexes on all 14 columns so that is one issue which I am aware off not sure if I change that to only lets say 4 to 5 columns on which I will be performing search/query via kibana dashboard - so that is something I still need to try off n see. Not sure once you have already loaded this much of data - can you just take indexes on few columns? like this situation. On Thursday, January 1, 2015 11:18:03 AM UTC-8, Arie wrote: > Hi > > How are your queries build up. In a default situation > Kibana queries all indices, it can help to query only > the indices that you need. Beside that there is a > dashboard option (preload fields) to improve your > query when it concerns a lot of data tot query every > time you refresh your panels. > > hth,, > Arie. > > Op woensdag 31 december 2014 21:25:37 UTC+1 schreef Bhumir Jhaveri: > > > Hey guys, > > > > I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - Here > > is the situation - I am currently running everything on single node - which > > I know is biggest problem n bottleneck. > > VM on which I am running is - 24gb ram- 8proc - 2TB storage space > > Here is snapshot of what I have on ES > > 12GB heap(used only 50% of what is available) > > 50 indices > > 370 shards > > 185 unassigned > > 757051595 docs > > 183.71GB is total space occupied (this is of last 7 days of data only) > > > > Now when I am running loading these data on my kibana dashboard, its > > running very slow. > > I agree that I need to split the data across multiple nodes - which is > > like 3 to 5 data node, 1 client node, 1 master node - so even with that > > configuration - it should run fine I guess may be for 10 to 15 days of data > > since data would be distributed across multiple data nodes (Again this is > > my assumption that it will go smooth) - > > so would this be sufficient or I should also tweak few other config > > params too - with which I will see some good performance and improvement? > > > > I know I am seriously not tweaking some of the important config which I > > should be but being little new to this world - I am still researching > > further on this. > > > > Should I move to some newer version of ES may be 1.3x or 1.4x which is > > compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the > > moment)? > > > > - Thanks, > > Bhumir -- 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/5ad5ac57-1bc9-4dbb-afb0-390067db6250%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5ad5ac57-1bc9-4dbb-afb0-390067db6250%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 2, 2015, 4:19pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/6 "2015-01-02T16:19:50Z")
Also I am planning to create multiple nodes here as - one single client node - which would be like with 16cpu and 60 gigs of RAM - and then alll data nodes with 8vcpu and 24gigs of ram and last the master with either 24gigs or 60 gigs - will this be a kind of correct design or I should change this to something. On Wednesday, December 31, 2014 12:25:37 PM UTC-8, Bhumir Jhaveri wrote: > Hey guys, > > I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - Here is > the situation - I am currently running everything on single node - which I > know is biggest problem n bottleneck. > VM on which I am running is - 24gb ram- 8proc - 2TB storage space > Here is snapshot of what I have on ES > 12GB heap(used only 50% of what is available) > 50 indices > 370 shards > 185 unassigned > 757051595 docs > 183.71GB is total space occupied (this is of last 7 days of data only) > > Now when I am running loading these data on my kibana dashboard, its > running very slow. > I agree that I need to split the data across multiple nodes - which is > like 3 to 5 data node, 1 client node, 1 master node - so even with that > configuration - it should run fine I guess may be for 10 to 15 days of data > since data would be distributed across multiple data nodes (Again this is > my assumption that it will go smooth) - > so would this be sufficient or I should also tweak few other config params > too - with which I will see some good performance and improvement? > > I know I am seriously not tweaking some of the important config which I > should be but being little new to this world - I am still researching > further on this. > > Should I move to some newer version of ES may be 1.3x or 1.4x which is > compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the > moment)? > > - Thanks, > Bhumir -- 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/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![crimondi](https://avatars.discourse-cdn.com/v4/letter/c/f05b48/32.png) [@crimondi](https://discuss.elastic.co/u/crimondi)\ **Post date:** [January 2, 2015, 5:34pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/7 "2015-01-02T17:34:08Z")
I agree with what has been said up to this point; adding more nodes and upgrading ES are good things to do. However, before beginning to spec out new hardware you should probably evaluate what your existing node is doing. Are you keeping metrics on what ES is doing? When I try to size my clusters I try to pay attention to what percent of the heap is being used for what purposes. How does disk I/O look? What are your CPUs doing when those queries come in? On Fri, Jan 2, 2015 at 11:19 AM, Bhumir Jhaveri [bhumir81@gmail.com](mailto:bhumir81@gmail.com) wrote: > Also I am planning to create multiple nodes here as - > one single client node - which would be like with 16cpu and 60 gigs of RAM > > - and then alll data nodes with 8vcpu and 24gigs of ram and last the master > with either 24gigs or 60 gigs - will this be a kind of correct design or I > should change this to something. > > On Wednesday, December 31, 2014 12:25:37 PM UTC-8, Bhumir Jhaveri wrote: > > > Hey guys, > > > > I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - Here > > is the situation - I am currently running everything on single node - which > > I know is biggest problem n bottleneck. > > VM on which I am running is - 24gb ram- 8proc - 2TB storage space > > Here is snapshot of what I have on ES > > 12GB heap(used only 50% of what is available) > > 50 indices > > 370 shards > > 185 unassigned > > 757051595 docs > > 183.71GB is total space occupied (this is of last 7 days of data only) > > > > Now when I am running loading these data on my kibana dashboard, its > > running very slow. > > I agree that I need to split the data across multiple nodes - which is > > like 3 to 5 data node, 1 client node, 1 master node - so even with that > > configuration - it should run fine I guess may be for 10 to 15 days of data > > since data would be distributed across multiple data nodes (Again this is > > my assumption that it will go smooth) - > > so would this be sufficient or I should also tweak few other config > > params too - with which I will see some good performance and improvement? > > > > I know I am seriously not tweaking some of the important config which I > > should be but being little new to this world - I am still researching > > further on this. > > > > Should I move to some newer version of ES may be 1.3x or 1.4x which is > > compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the > > moment)? > > > > - Thanks, > > Bhumir > > -- > 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/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Chris Rimondi | [http://twitter.com/crimondi](http://twitter.com/crimondi) | [securitygrit.com](http://securitygrit.com) -- 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/CA%2BqatLinSeX7Q3GSkxdEZenPB%3D%2BTWvguPZ6iiATmnKakStpi7Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CA%2BqatLinSeX7Q3GSkxdEZenPB%3D%2BTWvguPZ6iiATmnKakStpi7Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 2, 2015, 5:38pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/8 "2015-01-02T17:38:18Z")
Sure I will check that - is marvel better way to check these details? Though I have some rough idea of what the heap/cpus are doing - but since its hardware sizing so dont want to size them on guess work. On Friday, January 2, 2015 9:34:13 AM UTC-8, Chris Rimondi wrote: > I agree with what has been said up to this point; adding more nodes and > upgrading ES are good things to do. However, before beginning to spec out > new hardware you should probably evaluate what your existing node is doing. > Are you keeping metrics on what ES is doing? When I try to size my clusters > I try to pay attention to what percent of the heap is being used for what > purposes. How does disk I/O look? What are your CPUs doing when those > queries come in? > > On Fri, Jan 2, 2015 at 11:19 AM, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) > \\> wrote: > > > Also I am planning to create multiple nodes here as - > > one single client node - which would be like with 16cpu and 60 gigs of > > RAM - and then alll data nodes with 8vcpu and 24gigs of ram and last the > > master with either 24gigs or 60 gigs - will this be a kind of correct > > design or I should change this to something. > > > > On Wednesday, December 31, 2014 12:25:37 PM UTC-8, Bhumir Jhaveri wrote: > > > > > Hey guys, > > > > > > I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - Here > > > is the situation - I am currently running everything on single node - which > > > I know is biggest problem n bottleneck. > > > VM on which I am running is - 24gb ram- 8proc - 2TB storage space > > > Here is snapshot of what I have on ES > > > 12GB heap(used only 50% of what is available) > > > 50 indices > > > 370 shards > > > 185 unassigned > > > 757051595 docs > > > 183.71GB is total space occupied (this is of last 7 days of data only) > > > > > > Now when I am running loading these data on my kibana dashboard, its > > > running very slow. > > > I agree that I need to split the data across multiple nodes - which is > > > like 3 to 5 data node, 1 client node, 1 master node - so even with that > > > configuration - it should run fine I guess may be for 10 to 15 days of data > > > since data would be distributed across multiple data nodes (Again this is > > > my assumption that it will go smooth) - > > > so would this be sufficient or I should also tweak few other config > > > params too - with which I will see some good performance and improvement? > > > > > > I know I am seriously not tweaking some of the important config which I > > > should be but being little new to this world - I am still researching > > > further on this. > > > > > > Should I move to some newer version of ES may be 1.3x or 1.4x which is > > > compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the > > > moment)? > > > > > > - Thanks, > > > Bhumir > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > Chris Rimondi | [http://twitter.com/crimondi](http://twitter.com/crimondi) | [securitygrit.com](http://securitygrit.com) -- 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/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![crimondi](https://avatars.discourse-cdn.com/v4/letter/c/f05b48/32.png) [@crimondi](https://discuss.elastic.co/u/crimondi)\ **Post date:** [January 2, 2015, 6:20pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/9 "2015-01-02T18:20:36Z")
Marvel is good for looking at metrics. I find the \_cat API very helpful for spot checking. \_cat/nodes?v and \_cat/indices?v are two I use pretty frequently. We have a pretty tight statsd/graphite integration as well. On Fri, Jan 2, 2015 at 12:38 PM, Bhumir Jhaveri [bhumir81@gmail.com](mailto:bhumir81@gmail.com) wrote: > Sure I will check that - is marvel better way to check these details? > Though I have some rough idea of what the heap/cpus are doing - but since > its hardware sizing so dont want to size them on guess work. > > On Friday, January 2, 2015 9:34:13 AM UTC-8, Chris Rimondi wrote: > > > I agree with what has been said up to this point; adding more nodes and > > upgrading ES are good things to do. However, before beginning to spec out > > new hardware you should probably evaluate what your existing node is doing. > > Are you keeping metrics on what ES is doing? When I try to size my clusters > > I try to pay attention to what percent of the heap is being used for what > > purposes. How does disk I/O look? What are your CPUs doing when those > > queries come in? > > > > On Fri, Jan 2, 2015 at 11:19 AM, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) > > wrote: > > > > > Also I am planning to create multiple nodes here as - > > > one single client node - which would be like with 16cpu and 60 gigs of > > > RAM - and then alll data nodes with 8vcpu and 24gigs of ram and last the > > > master with either 24gigs or 60 gigs - will this be a kind of correct > > > design or I should change this to something. > > > > > > On Wednesday, December 31, 2014 12:25:37 PM UTC-8, Bhumir Jhaveri wrote: > > > > > > > Hey guys, > > > > > > > > I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - Here > > > > is the situation - I am currently running everything on single node - which > > > > I know is biggest problem n bottleneck. > > > > VM on which I am running is - 24gb ram- 8proc - 2TB storage space > > > > Here is snapshot of what I have on ES > > > > 12GB heap(used only 50% of what is available) > > > > 50 indices > > > > 370 shards > > > > 185 unassigned > > > > 757051595 docs > > > > 183.71GB is total space occupied (this is of last 7 days of data only) > > > > > > > > Now when I am running loading these data on my kibana dashboard, its > > > > running very slow. > > > > I agree that I need to split the data across multiple nodes - which is > > > > like 3 to 5 data node, 1 client node, 1 master node - so even with that > > > > configuration - it should run fine I guess may be for 10 to 15 days of data > > > > since data would be distributed across multiple data nodes (Again this is > > > > my assumption that it will go smooth) - > > > > so would this be sufficient or I should also tweak few other config > > > > params too - with which I will see some good performance and improvement? > > > > > > > > I know I am seriously not tweaking some of the important config which I > > > > should be but being little new to this world - I am still researching > > > > further on this. > > > > > > > > Should I move to some newer version of ES may be 1.3x or 1.4x which is > > > > compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the > > > > moment)? > > > > > > > > - Thanks, > > > > Bhumir > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c% > > > [40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > Chris Rimondi | [http://twitter.com/crimondi](http://twitter.com/crimondi) | [securitygrit.com](http://securitygrit.com) > > -- > 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/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Chris Rimondi | [http://twitter.com/crimondi](http://twitter.com/crimondi) | [securitygrit.com](http://securitygrit.com) -- 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/CA%2BqatLhSF8%3DBAgdjDJGdC6NONfCiGjRx94Rqhb6C03%2BBNqcOpA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CA%2BqatLhSF8%3DBAgdjDJGdC6NONfCiGjRx94Rqhb6C03%2BBNqcOpA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 2, 2015, 6:30pm UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/10 "2015-01-02T18:30:08Z")
I have never used it with \_cat api but I just tried it - its good - I already have kopf but doesnt tell you exactly when you're running in any query and its taking - so what all things its doing during that duration. On Friday, January 2, 2015 10:21:32 AM UTC-8, Chris Rimondi wrote: > Marvel is good for looking at metrics. I find the \_cat API very helpful > for spot checking. \_cat/nodes?v and \_cat/indices?v are two I use pretty > frequently. We have a pretty tight statsd/graphite integration as well. > > On Fri, Jan 2, 2015 at 12:38 PM, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) > \\> wrote: > > > Sure I will check that - is marvel better way to check these details? > > Though I have some rough idea of what the heap/cpus are doing - but since > > its hardware sizing so dont want to size them on guess work. > > > > On Friday, January 2, 2015 9:34:13 AM UTC-8, Chris Rimondi wrote: > > > > > I agree with what has been said up to this point; adding more nodes and > > > upgrading ES are good things to do. However, before beginning to spec out > > > new hardware you should probably evaluate what your existing node is doing. > > > Are you keeping metrics on what ES is doing? When I try to size my clusters > > > I try to pay attention to what percent of the heap is being used for what > > > purposes. How does disk I/O look? What are your CPUs doing when those > > > queries come in? > > > > > > On Fri, Jan 2, 2015 at 11:19 AM, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) > > > wrote: > > > > > > > Also I am planning to create multiple nodes here as - > > > > one single client node - which would be like with 16cpu and 60 gigs of > > > > RAM - and then alll data nodes with 8vcpu and 24gigs of ram and last the > > > > master with either 24gigs or 60 gigs - will this be a kind of correct > > > > design or I should change this to something. > > > > > > > > On Wednesday, December 31, 2014 12:25:37 PM UTC-8, Bhumir Jhaveri wrote: > > > > > > > > > Hey guys, > > > > > > > > > > I am facing some performance issues with ES(1.2.2)/Kibana(3.0.2) - > > > > > Here is the situation - I am currently running everything on single node - > > > > > which I know is biggest problem n bottleneck. > > > > > VM on which I am running is - 24gb ram- 8proc - 2TB storage space > > > > > Here is snapshot of what I have on ES > > > > > 12GB heap(used only 50% of what is available) > > > > > 50 indices > > > > > 370 shards > > > > > 185 unassigned > > > > > 757051595 docs > > > > > 183.71GB is total space occupied (this is of last 7 days of data only) > > > > > > > > > > Now when I am running loading these data on my kibana dashboard, its > > > > > running very slow. > > > > > I agree that I need to split the data across multiple nodes - which is > > > > > like 3 to 5 data node, 1 client node, 1 master node - so even with that > > > > > configuration - it should run fine I guess may be for 10 to 15 days of data > > > > > since data would be distributed across multiple data nodes (Again this is > > > > > my assumption that it will go smooth) - > > > > > so would this be sufficient or I should also tweak few other config > > > > > params too - with which I will see some good performance and improvement? > > > > > > > > > > I know I am seriously not tweaking some of the important config which > > > > > I should be but being little new to this world - I am still researching > > > > > further on this. > > > > > > > > > > Should I move to some newer version of ES may be 1.3x or 1.4x which is > > > > > compatible with Kibana 3.1.2(Definitely don't want to go kibana 4 at the > > > > > moment)? > > > > > > > > > > - Thanks, > > > > > Bhumir > > > > > > > > -- > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c% > > > > [40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ebf38e23-2ee6-4c7d-b658-e82aded6530c%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > Chris Rimondi | [http://twitter.com/crimondi](http://twitter.com/crimondi) | [securitygrit.com](http://securitygrit.com) > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e66dbee2-7c9b-461a-80d4-5c76e73e633b%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > Chris Rimondi | [http://twitter.com/crimondi](http://twitter.com/crimondi) | [securitygrit.com](http://securitygrit.com) -- 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/afebab25-7892-4d99-afea-59f1e8c6f122%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/afebab25-7892-4d99-afea-59f1e8c6f122%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:41am UTC](https://discuss.elastic.co/t/performance-slowness-issues-with-es/21444/11 "2017-07-06T00:41:08Z")