# Some performance checking questions **URL:** \ **Category:** Elasticsearch\ **Created:** [June 1, 2012, 6:04pm UTC](https://discuss.elastic.co/t/some-performance-checking-questions/7943 "2012-06-01T18:04:24Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Scott\_Decker](https://avatars.discourse-cdn.com/v4/letter/s/7bcc69/32.png) [@Scott\_Decker](https://discuss.elastic.co/u/Scott_Decker)\ **Post date:** [June 1, 2012, 6:04pm UTC](https://discuss.elastic.co/t/some-performance-checking-questions/7943/1 "2012-06-01T18:04:24Z")
Hello again. (Otis, yes, this weekend we are putting in sematext's monitor to try and help us out with the following!) We are trying to just debug slow updates to indexes and slow searches. anything to help what we should look for would be helpful. 1 - the cpus are working minimally on the 3 of the 4 nodes that we have 2 - if there is anything that i can guess at (until we add more monitoring this weekend) is that our primary node seems to be taking all of the updates and queries. could this be a results of drivers not using the other nodes? or, does all traffic supposed to go to the primary node? 3 - anything to turn on in elastic that would help track down usage patterns (we have multiple tools accessing the nodes) and see how we find the culprit? Hoping the sematext monitor of queries per node, and throughput will help analyze some of this as well. If we were to use something like YourKit to analyze, anything that would be a good pointer to why there are slow downs? Thanks, Scott ---
**Author:** ![Patrick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick/32/1437_2.png) [@Patrick](https://discuss.elastic.co/u/Patrick)\ **Post date:** [June 1, 2012, 7:10pm UTC](https://discuss.elastic.co/t/some-performance-checking-questions/7943/2 "2012-06-01T19:10:50Z")
Hey, Are you by any chance using rivers? and, what does your shard/replica setup look like? Single indice, or multiple indicies? And is it slow on the same query randomly? or just at startup? perhaps over different types of queries? ## Patrick > **[Patrick Ancillotti on about.me](https://about.me/patrick.ancillotti)** > > I live in New York. patrick eefy net On Fri, Jun 1, 2012 at 12:04 PM, Scott Decker [scott@publishthis.com](mailto:scott@publishthis.com) wrote: > Hello again. > > (Otis, yes, this weekend we are putting in sematext's monitor to try and > help us out with the following!) > > We are trying to just debug slow updates to indexes and slow searches. > > anything to help what we should look for would be helpful. > > 1 - the cpus are working minimally on the 3 of the 4 nodes that we have > 2 - if there is anything that i can guess at (until we add more monitoring > this weekend) is that our primary node seems to be taking all of the > updates and queries. > could this be a results of drivers not using the other nodes? or, does > all traffic supposed to go to the primary node? > 3 - anything to turn on in elastic that would help track down usage > patterns (we have multiple tools accessing the nodes) and see how we find > the culprit? > > Hoping the sematext monitor of queries per node, and throughput will help > analyze some of this as well. > > If we were to use something like YourKit to analyze, anything that would > be a good pointer to why there are slow downs? > > Thanks, > Scott ---
**Author:** ![Scott\_Decker](https://avatars.discourse-cdn.com/v4/letter/s/7bcc69/32.png) [@Scott\_Decker](https://discuss.elastic.co/u/Scott_Decker)\ **Post date:** [June 2, 2012, 1:54am UTC](https://discuss.elastic.co/t/some-performance-checking-questions/7943/3 "2012-06-02T01:54:11Z")
nope, no rivers. 4 servers, 4 cpu, 8 gigs of ram each our indexes are 4 shard 1 replica usually slow on queries. not random. I am just guessing that we have something misconfigured somewhere, just don't know where! Hopefully more monitoring will help track it down. Just wanted to see if there was anything that people could think of to narrow down a search into what could be the issue of 1 server taking the mass of load of updates/queries, instead of it being distributed to all nodes. On Friday, June 1, 2012 12:10:50 PM UTC-7, Patrick Ancillotti wrote: > Hey, > > Are you by any chance using rivers? and, what does your shard/replica > setup look like? Single indice, or multiple indicies? And is it slow on the > same query randomly? or just at startup? perhaps over different types of > queries? > > Hello again. > > > (Otis, yes, this weekend we are putting in sematext's monitor to try and > > help us out with the following!) > > > > We are trying to just debug slow updates to indexes and slow searches. > > > > anything to help what we should look for would be helpful. > > > > 1 - the cpus are working minimally on the 3 of the 4 nodes that we have > > 2 - if there is anything that i can guess at (until we add more > > monitoring this weekend) is that our primary node seems to be taking all of > > the updates and queries. > > could this be a results of drivers not using the other nodes? or, does > > all traffic supposed to go to the primary node? > > 3 - anything to turn on in elastic that would help track down usage > > patterns (we have multiple tools accessing the nodes) and see how we find > > the culprit? > > > > Hoping the sematext monitor of queries per node, and throughput will help > > analyze some of this as well. > > > > If we were to use something like YourKit to analyze, anything that would > > be a good pointer to why there are slow downs? > > > > Thanks, > > Scott ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [June 2, 2012, 2:00am UTC](https://discuss.elastic.co/t/some-performance-checking-questions/7943/4 "2012-06-02T02:00:54Z")
What about facets? The field cache can be a major slowdown of queries. How much memory are you allocating to Elasticsearch? BTW, Otis is probably on a plane right now heading to Berlin for Berlin Buzzwords. He helped me out this week to get SPM up and running. -- Ivan On Fri, Jun 1, 2012 at 6:54 PM, Scott Decker [scott@publishthis.com](mailto:scott@publishthis.com) wrote: > nope, no rivers. > > 4 servers, 4 cpu, 8 gigs of ram each > > our indexes are 4 shard 1 replica > > usually slow on queries. not random. > > I am just guessing that we have something misconfigured somewhere, just > don't know where! Hopefully more monitoring will help track it down. > Just wanted to see if there was anything that people could think of to > narrow down a search into what could be the issue of 1 server taking the > mass of load of updates/queries, instead of it being distributed to all > nodes. > > On Friday, June 1, 2012 12:10:50 PM UTC-7, Patrick Ancillotti wrote: > > > Hey, > > > > Are you by any chance using rivers? and, what does your shard/replica > > setup look like? Single indice, or multiple indicies? And is it slow on the > > same query randomly? or just at startup? perhaps over different types of > > queries? > > > > > Hello again. > > > > > > (Otis, yes, this weekend we are putting in sematext's monitor to try and > > > help us out with the following!) > > > > > > We are trying to just debug slow updates to indexes and slow searches. > > > > > > anything to help what we should look for would be helpful. > > > > > > 1 - the cpus are working minimally on the 3 of the 4 nodes that we have > > > 2 - if there is anything that i can guess at (until we add more > > > monitoring this weekend) is that our primary node seems to be taking all of > > > the updates and queries. > > > could this be a results of drivers not using the other nodes? or, does > > > all traffic supposed to go to the primary node? > > > 3 - anything to turn on in elastic that would help track down usage > > > patterns (we have multiple tools accessing the nodes) and see how we find > > > the culprit? > > > > > > Hoping the sematext monitor of queries per node, and throughput will help > > > analyze some of this as well. > > > > > > If we were to use something like YourKit to analyze, anything that would > > > be a good pointer to why there are slow downs? > > > > > > Thanks, > > > Scott ---
**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, 3:25am UTC](https://discuss.elastic.co/t/some-performance-checking-questions/7943/5 "2017-07-06T03:25:56Z")
Closed on July 6, 2017, 3:25am UTC