The system runs slowly: Clock drift, degraded performance, or pause-the-world detected

ignition Clock drift, degraded performance, and SQL slow logging
Appear irregularly
How should I locate the cause of the problem?
Does sql performance affect system stability?

  • Status > Systems > Overview

Recent Slow Response Events

System Response
Current Response Time
1ms
Recent Slow Response Events
Severity	Time	Event
11Jan2023 09:07:25	Clock drift, degraded performance, or pause-the-world detected. Max allowed deviation=1000ms, actual deviation=9554ms
11Jan2023 05:53:02	Clock drift, degraded performance, or pause-the-world detected. Max allowed deviation=1000ms, actual deviation=19415ms
11Jan2023 02:02:33	Clock drift, degraded performance, or pause-the-world detected. Max allowed deviation=1000ms, actual deviation=1666ms
10Jan2023 23:57:08	Clock drift, degraded performance, or pause-the-world detected. Max allowed deviation=1000ms, actual deviation=3826ms

Logs

Update progress event completed in suspiciously long time of 10999 mS for segment named
SingleConnectionDatasource	11Jan2023 09:07:08	The following stack successfully received a connection. A new attempt was blocked for over 30000 ms
SingleConnectionDatasource	11Jan2023 09:07:08	The following stack successfully received a connection. A new attempt was blocked for over 30000 ms

This is a common topic with many possible answers: overcommitted VMs, gateway and DB on same machine, poor memory settings in ignition.conf versus physical RAM, heap memory leaks (sometimes Ignition or driver bugs, sometimes poor scripting practices), et cetera. Some recent conversations with similar problems:

https://forum.inductiveautomation.com/search?q=clock%20drift%20order%3Alatest

2 Likes

This sort of thing is a very appropriate situation to call into tech support if you are not sure about the topics that @pturmel is talking about. As long as they are able to remote into the system they can poke around and see what is going on and help you optimize settings.

3 Likes