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

**URL:** <https://forum.inductiveautomation.com/t/the-system-runs-slowly-clock-drift-degraded-performance-or-pause-the-world-detected/68473>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [January 11, 2023, 8:44am UTC](https://forum.inductiveautomation.com/t/the-system-runs-slowly-clock-drift-degraded-performance-or-pause-the-world-detected/68473 "2023-01-11T08:44:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![770043297](https://avatars.discourse-cdn.com/v4/letter/7/b9bd4f/32.png) [@770043297](https://forum.inductiveautomation.com/u/770043297)\
**Post date:** [January 11, 2023, 8:44am UTC](https://forum.inductiveautomation.com/t/the-system-runs-slowly-clock-drift-degraded-performance-or-pause-the-world-detected/68473/1 "2023-01-11T08:44:14Z")

</div>

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

```python
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**

```python
Update progress event completed in suspiciously long time of 10999 mS for segment named

```

```python
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

```

---

<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:** [January 11, 2023, 1:07pm UTC](https://forum.inductiveautomation.com/t/the-system-runs-slowly-clock-drift-degraded-performance-or-pause-the-world-detected/68473/2 "2023-01-11T13:07:49Z")

</div>

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](https://forum.inductiveautomation.com/search?q=clock%20drift%20order%3Alatest)

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [January 11, 2023, 2:05pm UTC](https://forum.inductiveautomation.com/t/the-system-runs-slowly-clock-drift-degraded-performance-or-pause-the-world-detected/68473/3 "2023-01-11T14:05:50Z")

</div>

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.