# High CPU Usage after upgrade to 8.0.7 from 7.9.13 (MQTT Engine)

**URL:** <https://forum.inductiveautomation.com/t/high-cpu-usage-after-upgrade-to-8-0-7-from-7-9-13-mqtt-engine/32022>\
**Category:** General Discussion\
**Created:** [February 6, 2020, 8:45pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-after-upgrade-to-8-0-7-from-7-9-13-mqtt-engine/32022 "2020-02-06T20:45:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jordan.richardson](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@jordan.richardson](https://forum.inductiveautomation.com/u/jordan.richardson)\
**Post date:** [February 6, 2020, 8:45pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-after-upgrade-to-8-0-7-from-7-9-13-mqtt-engine/32022/1 "2020-02-06T20:45:51Z")

</div>

I have been noticing something strange while testing our new Ignition server installation. When I restored the backup without disabling, it will cause the CPU to max out, sometimes to the point of freezing. I was able to alleviate that by installing as disabled and enabling things one by one. I have now gotten it down to our MQTT Engine tag provider causing some issues. I will attach a few things to help troubleshoot, but I understand if not much can be done due to it being a cirrus link module. Additionally, all of our CPU percentages added together doesn’t even come close to what we’re showing as using on server, but that could just be a time lag issue between the two

[MQTT thread dump.txt](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/3b7624325e731ba8a69875d9b991df35169d1f99.txt) (8.3 KB)

 ![CPU%20usage%20vs%20MQTT%20usage](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/2f275ca28c18d41021db0efbefa23b3850fdf72d.png)