# Clock Drift Pause the World Detected **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [September 3, 2021, 2:56am UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585 "2021-09-03T02:56:59Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\ **Post date:** [September 3, 2021, 2:56am UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/1 "2021-09-03T02:56:59Z")
We have this decent server with J-Heap at 20GB. How ever, I just saw a pause the world detected, I though this could only be possible when the memory almost hit the heap, but in the time range where the event happened the memory is far from 20GB. In fact, the avg pick is always 10GB. **Question** What else can produce this clock drift? _Note: Not using Mozilla_ ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/d/add79cd1176307596cbcba392de80a911c44a25b.png) ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [September 3, 2021, 10:51am UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/2 "2021-09-03T10:51:35Z")
@dave.fogle had put up an article on this. > **[ClockDriftDetector warnings in the Gateway Console](https://support.inductiveautomation.com/hc/en-us/articles/360047576511-ClockDriftDetector-warnings-in-the-Gateway-Console)** > > Issue: > The Gateway console shows warnings posted by the ClockDriftDetector logger, with the following message: "Clock drift, degraded performance, or pause-the-world detected"; the messa... ---
**Author:** ![321liftoff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/321liftoff/32/27544_2.png) [@321liftoff](https://forum.inductiveautomation.com/u/321liftoff)\ **Post date:** [September 3, 2021, 11:52am UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/3 "2021-09-03T11:52:46Z")
I have found that these messages don’t appear in the log until I start opening the performance pages, such as the threads diagnostics, and overall CPU/ram usage. I didn’t see this explantation in the article, so don’t know if that’s expected it not. ---
**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 3, 2021, 11:54am UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/4 "2021-09-03T11:54:00Z")
Your actual delays are just over the limit. Suggesting the JVM’s pause target is one second. You should set that much lower. I typically set a 100 or even 50 millisecond target. Share your ignition.conf file… ---
**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 3, 2021, 11:54am UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/5 "2021-09-03T11:54:58Z")
> [@321liftoff](#): > > such as the threads diagnostics This one. Yes, expected. Avoid looking at threads, as collecting the details on them disrupts the JVM itself. ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [September 3, 2021, 3:05pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/6 "2021-09-03T15:05:35Z")
Could you expound on this a bit? ---
**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 3, 2021, 3:08pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/7 "2021-09-03T15:08:51Z")
The JVM can’t capture thread details while they are running. So there’s a brief pause when collection information about all threads for a thread dump. For a busy system with lots of threads, this is noticeable. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [September 3, 2021, 3:09pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/8 "2021-09-03T15:09:13Z")
It seems a little suspicious that the events are frequently 10s apart or a multiple of 10s. Is this really 7.9? Is there a 10s gateway timer script or anything like that? ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [September 3, 2021, 3:13pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/9 "2021-09-03T15:13:18Z")
Ok… And dropping the pause length will help as well? How do you tune that out properly? ---
**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 3, 2021, 3:13pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/10 "2021-09-03T15:13:21Z")
You should have a line in ignition.conf like so: ```auto wrapper.java.additional.2=-XX:MaxGCPauseMillis=100 ``` The G1GC algorithm will run more often when pauses exceed that threshold, and run less often when pauses are substantially less. It is a heuristic, not a hard rule, but G1GC is pretty good at keeping pauses under the target maximum. ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [September 3, 2021, 3:13pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/11 "2021-09-03T15:13:48Z")
Awesome. Always love learning better ways to tune these systems. ---
**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 3, 2021, 3:14pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/12 "2021-09-03T15:14:51Z")
Isn’t 10 seconds the refresh pace on gateway status pages? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [September 3, 2021, 3:23pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/13 "2021-09-03T15:23:19Z")
Not sure. I think the thread viewer page is 5s. Don’t know about others, but that’s the heaviest one I think. ---
**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\ **Post date:** [September 10, 2021, 9:42pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/14 "2021-09-10T21:42:36Z")
Sorry for delay. Thanks for all info there. Indeed, as some one mentioned. This happened due to checking threads page as shows: [https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/1/f1fd44888020bdfc6b1a89ecf7c6eb8039563d3d.mp4](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/1/f1fd44888020bdfc6b1a89ecf7c6eb8039563d3d.mp4) ---
**Author:** ![joshi.pradnya06](https://avatars.discourse-cdn.com/v4/letter/j/e68b1a/32.png) [@joshi.pradnya06](https://forum.inductiveautomation.com/u/joshi.pradnya06)\ **Post date:** [March 11, 2026, 8:17pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/15 "2026-03-11T20:17:18Z")
Hi, I was experiencing a major lag while running the ignition app so I checked the log files and found the same Clock Drift, degraded performance entry. So after investigating into it further found out that the CPU & memory usage was more that 85%, so tried rebooting the server and the server PC and it worked (CPU memory usage was brought down in range of 30-40%). The system response was also improved. However I wanted to make sure if we dont run into this issue again. So checked the ignition.conf file refering to your comment above and found that the line is as follow: wrapper.java.additional.2 = –add-opens=java.base/java.lang=ALL-UNNAMED Do I update that line to: wrapper.java.additional.2=-XX:MaxGCPauseMillis=100 And will doing that fix the issue for the future? I can share the ignition.conf file as well if needed. Thanks ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [March 11, 2026, 8:29pm UTC](https://forum.inductiveautomation.com/t/clock-drift-pause-the-world-detected/50585/16 "2026-03-11T20:29:10Z")
It's unlikely that this parameter will help you in the future. You should give support a call and talk to them about the issue.