vmware vs virtualbox performance multithreading

Not running multiple concurrent VMs with conflicting resources in a single host (like Virtual Private Server reselling).

Trying to do long tasks (where even 1% better performance is to take).

Trying to allow single-threaded applications to run on a physical core instead of a logical core.

The difference, however, is negligible for most tasks unless you are: The quick conclusion is that using more sockets helps a lot.

Windows Server 2012 R2 Datacenter as Client with 54GB RAM (I got as many licenses as I want, I was a Microsoft Certified Trainer for 2 years).

Linux host (Ubuntu 16.04) with Intel i7–3930K (6 Physical Cores, 12 Logical Cores, 3.20 GHz, 3.80 GHz turbo boost) + 64GB RAM.

I am still using the same configuration as previously: What if we go through the licensing issues, and use Windows Server? This is what we are going to explore now. In the previous part, we found out using the reverse of a long setup (12 cores, 1 socket) was performing the best when we could not use a long setup directly (due to licensing issues, cf Windows Desktops). Non-Kaggle post about the impact of Virtualized CPU cores / Sockets on Machine Learning / Optimization problems, specifically on xgboost and VMware (Linux host, Windows client). Virtualization & (Hyperthreading) Machine Learning Performance (Windows) (Part 2)

Vmware vs virtualbox performance multithreading