# Single Node Performance and periodic latency spikes **URL:** \ **Category:** Elasticsearch\ **Created:** [July 30, 2019, 9:10am UTC](https://discuss.elastic.co/t/single-node-performance-and-periodic-latency-spikes/192855 "2019-07-30T09:10:12Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Samy\_Ateia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samy_ateia/32/51314_2.png) [@Samy\_Ateia](https://discuss.elastic.co/u/Samy_Ateia)\ **Post date:** [July 30, 2019, 9:10am UTC](https://discuss.elastic.co/t/single-node-performance-and-periodic-latency-spikes/192855/1 "2019-07-30T09:10:12Z")
Hi Everyone, we are currently conducting experiments to evaluate Elasticsearch for our Use-Case. While doing performance tests on a single Node instance, we came across some periodic search-latency spikes. We are running an OR query with a static and random string to prevent caching. We ramp up the concurrent users from 1-50. We tried both single shard and 5 shards index. The query contains a lot of aggregations, content specific weighting base on a function\_score query multiple filters and field collapsing. Single shard performance seems to be worse for few concurrent users but better for 20-50 concurrent users. Both single and 5 shard indices are showing latency spikes every 2-3 Minutes. (see atached jmeter graphs). Can this be related to garbage collection? Did anyone come across similar behavior before and knows a mitigation strategy? Best Samy ![singleshard](https://us1.discourse-cdn.com/elastic/original/3X/b/6/b60601875f2ec77aaa511d83479806ed97c68843.png) ![5shards](https://us1.discourse-cdn.com/elastic/original/3X/1/e/1ef524f9d116287c900fa31483702b88e09a3ed6.png) ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [July 30, 2019, 10:14am UTC](https://discuss.elastic.co/t/single-node-performance-and-periodic-latency-spikes/192855/2 "2019-07-30T10:14:27Z")
Have you correlated the spikes again st GC? ---
**Author:** ![Samy\_Ateia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samy_ateia/32/51314_2.png) [@Samy\_Ateia](https://discuss.elastic.co/u/Samy_Ateia)\ **Post date:** [July 30, 2019, 11:01am UTC](https://discuss.elastic.co/t/single-node-performance-and-periodic-latency-spikes/192855/3 "2019-07-30T11:01:20Z")
Working on it. Wer are using the hostes aws elasticsearch service, i'm figuring out a way to get exact GC data. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [July 30, 2019, 12:10pm UTC](https://discuss.elastic.co/t/single-node-performance-and-periodic-latency-spikes/192855/4 "2019-07-30T12:10:51Z")
What kind of instance are you using? ---
**Author:** ![Samy\_Ateia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samy_ateia/32/51314_2.png) [@Samy\_Ateia](https://discuss.elastic.co/u/Samy_Ateia)\ **Post date:** [July 31, 2019, 7:34am UTC](https://discuss.elastic.co/t/single-node-performance-and-periodic-latency-spikes/192855/5 "2019-07-31T07:34:29Z")
c5.12xlarge with around 250.000 documents ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 28, 2019, 7:34am UTC](https://discuss.elastic.co/t/single-node-performance-and-periodic-latency-spikes/192855/6 "2019-08-28T07:34:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.