Ticket #10485 (closed defect: obsolete)
Excessive system-wide timer resolution on Windows host when running any guest
|Reported by:||merkel||Owned by:|
The moment a VM is started, the system-wide timer resolution in the host is bumped to 2000Hz. (AFAIK the only way to go past the usual 1000Hz is calling NtSetTimerResolution directly.)
This causes more interrupts and therefore more CPU and power usage.
2000Hz seems a bit excessive. Apparently the reason is that SUPDrv.c tries to set it to 1024 Hz, but Windows rounds up requests, so it goes from 1000 to 2000.
Are 1024 Hz really necessary? If 1000 would suffice, could this be relaxed to 1000 for Windows hosts?