# CPU and RAM problems: Clock events and Garbage Collector configuration **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [November 14, 2023, 9:50am UTC](https://forum.inductiveautomation.com/t/cpu-and-ram-problems-clock-events-and-garbage-collector-configuration/81850 "2023-11-14T09:50:13Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [November 14, 2023, 2:05pm UTC](https://forum.inductiveautomation.com/t/cpu-and-ram-problems-clock-events-and-garbage-collector-configuration/81850/4 "2023-11-14T14:05:39Z")
Related topic: > [@When 'Clock Drift' occurs continuously, which part should be checked?](https://forum.inductiveautomation.com/t/when-clock-drift-occurs-continuously-which-part-should-be-checked/81633/4): > > If your clock drift corresponds to the GC pause-the-world event for the sawtooth drop-offs, then the amount of garbage being cleaned up in each is too much for your CPUs to do quickly. Please add GC logging to your ignition.conf and post the results for a few sawtooth cycles. Something like this: wrapper.java.additional.20=-Xloggc:logs/javagc-%WRAPPER\_TIME\_YYYYMMDDHHIISS%.log wrapper.java.additional.21=-XX:+PrintGCDetails Make sure the 20 and 21 are unique integers in the list of additional … --- _[View the full topic](https://forum.inductiveautomation.com/t/cpu-and-ram-problems-clock-events-and-garbage-collector-configuration/81850)._