# 7.6.1rc4 Clock drift detector **URL:** \ **Category:** Ignition\ **Created:** [May 21, 2013, 1:06pm UTC](https://forum.inductiveautomation.com/t/7-6-1rc4-clock-drift-detector/6543 "2013-05-21T13:06:00Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\ **Post date:** [May 21, 2013, 1:06pm UTC](https://forum.inductiveautomation.com/t/7-6-1rc4-clock-drift-detector/6543/1 "2013-05-21T13:06:00Z")
Hello, has anybody an idea what this message means? (I’m quite sure i didn’t hit the worlds pause button…) `INFO | jvm 1 | 2013/05/21 14:46:37 | WARN [ClockDriftDetector] [14:46:37,746]: Clock drift, degraded performance, or pause-the-world detected. INFO | jvm 1 | 2013/05/21 14:46:37 | lastTime=Tue May 21 14:46:26 CEST 2013 INFO | jvm 1 | 2013/05/21 14:46:37 | currentTime=Tue May 21 14:46:37 CEST 2013 INFO | jvm 1 | 2013/05/21 14:46:37 | deviation from expected 1000ms delta=10348ms. INFO | jvm 1 | 2013/05/21 14:50:33 | WARN [ClockDriftDetector] [14:50:33,249]: Clock drift, degraded performance, or pause-the-world detected. INFO | jvm 1 | 2013/05/21 14:50:33 | lastTime=Tue May 21 14:50:22 CEST 2013 INFO | jvm 1 | 2013/05/21 14:50:33 | currentTime=Tue May 21 14:50:33 CEST 2013 INFO | jvm 1 | 2013/05/21 14:50:33 | deviation from expected 1000ms delta=10061ms. INFO | jvm 1 | 2013/05/21 14:54:14 | WARN [ClockDriftDetector] [14:54:14,795]: Clock drift, degraded performance, or pause-the-world detected. INFO | jvm 1 | 2013/05/21 14:54:14 | lastTime=Tue May 21 14:54:02 CEST 2013 INFO | jvm 1 | 2013/05/21 14:54:14 | currentTime=Tue May 21 14:54:14 CEST 2013 INFO | jvm 1 | 2013/05/21 14:54:14 | deviation from expected 1000ms delta=11075ms. ` ---
**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:** [May 21, 2013, 1:10pm UTC](https://forum.inductiveautomation.com/t/7-6-1rc4-clock-drift-detector/6543/2 "2013-05-21T13:10:55Z")
Either you’re debugging and hitting break points, garbage collection is taking 10 seconds, auto backups are taking 10 seconds, or you’re experiencing regular 10 second movements in the system clock. It’s there to warn you that the system is slower than it should be in some way… (The idea may be a bit flawed… But we’ve had an influx of people running ignition in VMs with weird things happening to their system clock or long pauses to the system happening.) ---
**Author:** ![danielsoar](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@danielsoar](https://forum.inductiveautomation.com/u/danielsoar)\ **Post date:** [May 23, 2013, 5:45am UTC](https://forum.inductiveautomation.com/t/7-6-1rc4-clock-drift-detector/6543/3 "2013-05-23T05:45:10Z")
Just FYI ive pulled my ignition server out of virtualisation and put it on a physical machine. Had no problems since then Kevin. Ill try it again after the next upgrade on the VM but im just glad to be back up and running. ---
**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:** [May 23, 2013, 2:21pm UTC](https://forum.inductiveautomation.com/t/7-6-1rc4-clock-drift-detector/6543/4 "2013-05-23T14:21:15Z")
![:thumb_left:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/e26afb081ddde6df016df6ee49159cf56aaca688.gif ":thumb\_left:") ---
**Author:** ![Dravik](https://avatars.discourse-cdn.com/v4/letter/d/e274bd/32.png) [@Dravik](https://forum.inductiveautomation.com/u/Dravik)\ **Post date:** [May 23, 2013, 2:29pm UTC](https://forum.inductiveautomation.com/t/7-6-1rc4-clock-drift-detector/6543/5 "2013-05-23T14:29:52Z")
I run ours on a VM as well. Because it is still Win2k3, I use the /usepmtimer boot option and AD timesync to keep the drift from happening. (One little note, If you are VMd and you have an option to have the hypervisor sync the PC clock, make sure that isnt’ fighting with WinTime) ---
**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:** [May 23, 2013, 2:45pm UTC](https://forum.inductiveautomation.com/t/7-6-1rc4-clock-drift-detector/6543/6 "2013-05-23T14:45:20Z")
The really treacherous thing about Dan’s VM situation is that it turns out the clock isn’t really drifting by any dramatic amount, but that the System.currentTimeMillis() call is sporadically returning timestamps from the future (hours, days) and then returning back to normal behavior immediately after. VMs suck 😠 ---
**Author:** ![Dravik](https://avatars.discourse-cdn.com/v4/letter/d/e274bd/32.png) [@Dravik](https://forum.inductiveautomation.com/u/Dravik)\ **Post date:** [May 23, 2013, 3:10pm UTC](https://forum.inductiveautomation.com/t/7-6-1rc4-clock-drift-detector/6543/7 "2013-05-23T15:10:31Z")
If it is Hyper-V, the /usepmtimer is highly recommended w/ Win2003 multiproc/core. And yeah, I hate dealing w/ time on VMs. Years and years of expecting time to be hardware based really makes time management a pita.