Yes there are a couple of ways but they are not easy to interpret.
Profiler Scan (this will work better after 2024.2 is released with Python 3.12 support as it will show the thread info). But is still worth trying now:
Also Py-Spy.
Run the scan and ask for help interpreting the results in this topic if you need it:
The profiler looks very interesting. As we are only a few days away from 2023.02, I’ll just wait for the update. After all, it has been running like this for over a month now.
I’ll come back here and let you know if it helped when the update is released.
Hi Boerny,
I would be curious how you finally solved this issue. Same phenomenon on my side. Many nightly backups go well but every now and then there is one where the CPU load stays at around 30% in my case. Usually it’s around 1%. Only a restart of the entire system does help, than the CPU load is back to 1% again. I do daily backups during the night. After a week or so the CPU load stays high, even if the backup job is finished. I trigger the backup with an automation rule.
Cheers
I am also finding this to be the case, due to Proxmox backups. I check the HASS VM cpu stats in Proxmox , and the container CPU spikes right when the backup begins within Proxmox. But then it never reduces back to normal. Also finding if I have a browser open with a HASS tab, the browser cpu spikes and stays running high too. It is only resolvable by restarting the entire HASS container within Proxmox.
Even stranger (to me) is that when I use Glances to investigate the CPU usage, it appears to be “python3” as the culprit of high CPU usage. But again, this never happens until the Proxmox backup happens. Perhaps some Integration goes on a runaway loop while Proxmox is freezing certain files for backup, idk.