High CPU usage in idle state under PBS 4.0

haven't seen that one.. did you reboot after the upgrade?
 
The PBS is running on a QNAP TS-464 (Intel N5105) - been running for over 18 months with PBS 3.x without issue - assigned 4GB memory and 2 vCPUs
In idle there was very little CPU usage (averaging around 16%)
 
it would be interesting to find out what exactly is using the CPU or keeping it busy - in your screenshot the PBS services only make up a fraction of it..
 
did you configure your htop to hide kernel threads maybe?
 
Oddly, on the virtualized VM itself - the CPU seems much lower ? So maybe the PBS statistics are not the truth?

1755090560060.png
 
what do the PSI stats say?
 
`cat /proc/pressure/cpu` ;)
 
root@PBSFox:~# cat /proc/pressure/cpu
some avg10=8.41 avg60=7.25 avg300=6.99 total=376957203
full avg10=0.00 avg60=0.00 avg300=0.00 total=0
 
okay, so it seems this is mostly some reporting artifact, maybe caused by your unusual environment..
 
You tell me ;) Like I said - same setup with PBS 3.x worked as expected - only after the in place update to PBS 4.0 I'm having this problem. Maybe I need to perform a fresh install ?? Not sure how to migrate the old system config over - I'll have re-register all the nodes again with the new fingerprint :( Very odd indeed!
 
well, the upgrade brings a new kernel, and that might change some behaviour w.r.t. your virtualization environment, for example. you're the first one to report such behaviour, so I suspect virtualization station to maybe be the culprit..
 
Very likely - although I believe I was using the back ported 6.14bpo kernel on the PBS 3.x version before ?!? I might move the PBS to a better machine and do the datastore over NFS to the QNAP - instead of directly on the NAS with local disk image - although I'm worried about performance using NFS over the network (got 2x2.5G on the NAS) - guess it's time to play around.

Is there a best practice procedure when creating a fresh install and moving configs from an older instance ??
 
the config should be fairly self-contained in /etc/proxmox-backup and all the data in the datastore.. don't let two PBS instances access the same datastore in parallel though!
 
  • Like
Reactions: rfox
Just to understand - I install a new instance and simply copy the whole /etc/proxmox-backup folder from the other one - point to the datastore and all is good ?? Is it really that easy :oops:
 
You must log in or register to reply here.
Top Bottom