# GC s1 always used 100%, never less than 100%

**URL:** <https://discuss.elastic.co/t/gc-s1-always-used-100-never-less-than-100/111076>\
**Category:** Elasticsearch\
**Created:** [December 11, 2017, 11:19am UTC](https://discuss.elastic.co/t/gc-s1-always-used-100-never-less-than-100/111076 "2017-12-11T11:19:45Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [December 12, 2017, 10:30am UTC](https://discuss.elastic.co/t/gc-s1-always-used-100-never-less-than-100/111076/4 "2017-12-12T10:30:00Z")

</div>

I think this is a visualization problem of `jstat`. The G1 heap layout is quite different to heap layouts of previous garbage collectors and the `jstat` tool seems not to have been adapted.

If you want to analyze GC behavior the better option is to enable GC logs and to look at them instead. If you are interested in detailed information about region sizes you can turn add `-XX:+PrintHeapAtGC` to your JVM options.

For a more thorough explanation of how G1 works, you can watch e.g. the following video by Monica Beckwith:

---

_[View the full topic](https://discuss.elastic.co/t/gc-s1-always-used-100-never-less-than-100/111076)._