Thanks for the head’s up baudlord! I think there are 2 things: - the high CPU usage on garbage collection - you have a lot of datasets (probably related to docker, can you confirm?)
Definitively, your override.conf will be of help to have logs the next time you get this high CPU so that we can see what is exactly happening / when this (inifite?) loops occurs. We still can’t reproduce here. I think it’s related to the amount of datasets created by docker, but in any case, it will be good to fix the CPU issue. FYI, on the docker side, we fixed it yesterday on groovy and expect to SRU it to 20.04 LTS in the coming days (https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1879473). However, if possible, it would be good to have your high CPU logs before you test this fix, so that we can analyze and fix it, as probably other setup can create this. Keep us posted, and thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870461 Title: zsysd uses more than half of CPU and disk IO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1870461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
