Hyper-V XP pro guest: tweaking number of processors
I have a XP pro (32 bit) Hyper-V guest running on Windows server 2012 R2 std
I ran a test application with various quantities of virtual processors:
1 Processor application ran slow.
4 Processors application ran faster.
32 Processors application ran very slow.
Is there a better way to find the optimum setting than trial & error?
Thx,
I ran a test application with various quantities of virtual processors:
1 Processor application ran slow.
4 Processors application ran faster.
32 Processors application ran very slow.
Is there a better way to find the optimum setting than trial & error?
Thx,
Cliff Galiher
Not really, and this isn't necessarily because of Hyper-V. Keep in mind that XP released before multi-core processors were common, so multi-threading is not its strongest ability. If you assign more processors than you have physical cores, you are now introducing some overhead to Hyper-V that'll hurt you as well. So I think you hit two extremes. One with too little, and the other you just overwhelmed Hyper-V. On modern hardware, 1 processor is usually fine for XP though, so I suspect you have some unrelated issues going on as well. Hyper-V has a ton of performance counters you can use to get insight into what is actually happening on the machine.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hyper-V limits XP Pro to 2 virtual CPUs (vCPUs).
That's going to be your maximum.
As Lee mentioned, your host's workloads could also be a factor.
That's going to be your maximum.
As Lee mentioned, your host's workloads could also be a factor.