About pve7 default cpu scheduler

[hazaki]

As the default cpu scheduler of pve7 has changed from "performance" to "schedutil", this will result in lower vm performance.It is not only delay-sensitive VMs that are affected, but ordinary VMs will also be affected.
I know it is easy to change this, but I think that as a virtualization platform, "schedutil" should not be used as the default value.

 

[t.lamprecht]

Schedutil is quite a nice trade-off between really good performance, simplicity while also saving power if not required.
Also, it does not waste more computing power in elaborate algorithms than then actually provided by said algorithms, but still reacts very fast and good to actual load.

Did you see some drops in performance due to that change?

 

[hazaki]

Schedutil is quite a nice trade-off between really good performance, simplicity while also saving power if not required.
Also, it does not waste more computing power in elaborate algorithms than then actually provided by said algorithms, but still reacts very fast and good to actual load.

Did you see some drops in performance due to that change?

Yes, all VMs have experienced varying degrees of decline.This is true even for a fresh installation.
The bios has been adjusted, including C1E, speedshift and so on.
The processor is i3 10100, the frequency is approximately stable at 2.4Ghz, and rarely fluctuates with the load.
If adjusted to performance, the frequency is 3.6GHz, turbo boost can also be triggered, and the full load will stabilize at 4.1GHz.
In theory, it doesn't matter if the frequency is lower.In theory, it doesn't matter if the frequency is lower, but vRouter will experience strange performance degradation, and even 300Mbps traffic cannot be reached.
I don’t know if PCIE will be affected