# NIOEventLoop and high cpu usage

**URL:** <https://forum.inductiveautomation.com/t/nioeventloop-and-high-cpu-usage/38542>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [September 10, 2020, 5:18am UTC](https://forum.inductiveautomation.com/t/nioeventloop-and-high-cpu-usage/38542 "2020-09-10T05:18:11Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 10, 2020, 12:55pm UTC](https://forum.inductiveautomation.com/t/nioeventloop-and-high-cpu-usage/38542/3 "2020-09-10T12:55:59Z")

</div>

Also, switch to G1GC. The concurrent-mark-sweep garbage collector is horrible. Start here:

> [@Migrating to Java G1GC garbage collection](http://forum.inductiveautomation.com/t/migrating-to-java-g1gc-garbage-collection/18638/2):
>
> Oracle backed out of its announced rollout of G1GC as the default in Java 8. It supposedly is the default finally in Java 9, but I haven’t switch to 9 yet. Adding the switches won’t hurt anything if its the default.

---

_[View the full topic](https://forum.inductiveautomation.com/t/nioeventloop-and-high-cpu-usage/38542)._