Re: Domain-0 CPU pinning - is it still a best practice?

[Brian Blood <brian@xxxxxxxxxxxx>]

Some things I feel comfortable entrusting to the hypervisor scheduler; some things I don’t.

For the latter, it gives me more piece of mind to dedicated full blocks of resources.

IO and RAID ops (being core to almost any other operation performed on the machine) fall into that second category.

My $0.02.

On Jan 31, 2021, at 3:43 PM, Pierre-Philipp Braun <pbraun@xxxxxxxxxxxx> wrote:

cpus = "all,^0,^1"

I rather share all CPUs and let the scheduler prioritize dom0 as such (default weight is 256):

xl sched-credit2 --domain=0 --weight=512

The only drawback is that I need to be careful on what I do on the host, to let some juice available for the guests.  The good thing about it is that the dom0 also shares all cores, I guess)

Sorry it's not a definitive answer, as I did not compare and stress-bench this against an old-school pinning setup.