# When 'Clock Drift' occurs continuously, which part should be checked?

**URL:** <https://forum.inductiveautomation.com/t/when-clock-drift-occurs-continuously-which-part-should-be-checked/81633>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [November 8, 2023, 2:20am UTC](https://forum.inductiveautomation.com/t/when-clock-drift-occurs-continuously-which-part-should-be-checked/81633 "2023-11-08T02:20:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [November 8, 2023, 1:28pm UTC](https://forum.inductiveautomation.com/t/when-clock-drift-occurs-continuously-which-part-should-be-checked/81633/4 "2023-11-08T13:28:07Z")

</div>

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:

```auto
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 java arguments.

---

_[View the full topic](https://forum.inductiveautomation.com/t/when-clock-drift-occurs-continuously-which-part-should-be-checked/81633)._