# ES 2.4 GC time % unmanageable. Any tip?

**URL:** <https://discuss.elastic.co/t/es-2-4-gc-time-unmanageable-any-tip/279124>\
**Category:** Elasticsearch\
**Created:** [July 20, 2021, 7:44am UTC](https://discuss.elastic.co/t/es-2-4-gc-time-unmanageable-any-tip/279124 "2021-07-20T07:44:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\
**Post date:** [July 20, 2021, 7:44am UTC](https://discuss.elastic.co/t/es-2-4-gc-time-unmanageable-any-tip/279124/1 "2021-07-20T07:44:04Z")

</div>

Hey there, I am trying to find the sweet spot for my application.  
I got these results:

_DATA nodes 8cpu-32gb ram with 16gb heap size and 8gb young heap size_  
_GC time % is generally around 5% (this is in case the limit)_

_DATA nodes 8cpu-64gb ram with 16gb heap size and 8gb young heap size_  
_GC time % is generally over 10%_

In the second scenario, I doubled up the DATA's ram to try to handles more events. Instead, I am able to process lower events because DATA resources are stressed by GC time %.  
All the surrounded details (input traffic, indices size, number of shards etc etc) are the same.  
I read several docs on blog and also somewhere else but I cannot find a way to understand correctly this behaviour. I just know that I should find a way to decrease that GC time % value.

is there anyone that can help me? The ES version is so old, I know. I have another branch with latest one but values cannot be compared.

---

<div class="post-metadata">

**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 20, 2021, 8:26am UTC](https://discuss.elastic.co/t/es-2-4-gc-time-unmanageable-any-tip/279124/2 "2021-07-20T08:26:03Z")

</div>

What is the full output of the cluster stats API? Do you have any non-default cluster or JVM settings?

---

<div class="post-metadata">

**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\
**Post date:** [July 20, 2021, 8:44am UTC](https://discuss.elastic.co/t/es-2-4-gc-time-unmanageable-any-tip/279124/3 "2021-07-20T08:44:59Z")

</div>

Cluster is composed by 3 simple MASTER and 3 DATA.  
No particular settings. Regarding JVM I am just specifying Xmx-Xms-Xmn  
I cannot post the \_stats output due to limited number of chars in the post 😢

---

<div class="post-metadata">

**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 20, 2021, 9:21am UTC](https://discuss.elastic.co/t/es-2-4-gc-time-unmanageable-any-tip/279124/4 "2021-07-20T09:21:32Z")

</div>

Then please make it available some other way, e.g. through a gist or using paste in or some similar tool.

---

<div class="post-metadata">

**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\
**Post date:** [July 20, 2021, 9:37am UTC](https://discuss.elastic.co/t/es-2-4-gc-time-unmanageable-any-tip/279124/5 "2021-07-20T09:37:04Z")

</div>

\_stats

[https://paste.in/l0AIC4](https://paste.in/l0AIC4)

\_nodes/stats

[https://paste.in/iXx0cw](https://paste.in/iXx0cw)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 17, 2021, 9:37am UTC](https://discuss.elastic.co/t/es-2-4-gc-time-unmanageable-any-tip/279124/6 "2021-08-17T09:37:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
