Very large load on server after upgrade to 1.37.42

[baekmark]

Hi all
I have been using zm for many years and lastly with Ubuntu 16.04 LTS. Every thing was running smoothly with 6 cameras all at super high resolution like 4 and 5K. I’m using HikVision

Last week it was time to upgrade to latest OS, so I got it to 22.04 LTS and zm was updated to 1.37.42. That broke all cameras as I was using Remote and RTSP

After a lot of trial and error I got it to work with Ffmpeg, but now my server feels very busy with very slow update on screen.

Am I missing something?

Thanks in advance

[mikauskas]

I had a load over 22 with 4 1080p cameras and version 1.36.33. For me it was caused by mysql. Reduced by disabling mysql logging.
https://simonauer.medium.com/disabling- ... 3ce9aeac2e
Also, reduced by settling cameras function to Nodect and disabling analysis, decoding. At cameras storage disable save JPEGs.
Video Writer - Camera Passthrough

[baekmark]

Update/Solved

I think I nailed it
The harddrive was a spinning 500GB drive that is very old, but still working. I did suspect that it was a Wait for IO issue, so I Cloned the drive using CloneZilla onto a Samsung 500 GB SSD, and the server is now running very smooth.

@mikauskas Thanks for your reply, but the thing is, that the only thing that has been changed is the OS (Ubuntu 16.04 --> 18.04 --> 20.04 --> 22.04) and Zoneminder was updated to latest version. The very server and cameras are the same. The resolution on each camera is 2688x1520.

The upgrade of the disk was done Saturday morning and the server has been running very smooth with a load of 2 - 2.80.

[mikauskas]

Wait for IO issue usually means HDD is failing, perhaps just finished it.

[baekmark]

I was on my todo list, but as a husbond, dad, granddad, house owner and working there are just so many things on the plate.

It was super easy. Made a USB stick with CloneZilla, and booted, selected the device to device, and an hour later, I was able to boot off the new SSD, without changing a single line of code.

But thanks for your reply