With Samsung RAPID mode disabled, disk performance in the VirtualBox guest ranged from 12% slower to 4% faster than the physical host. 
Enabling/disabling Hyper-Threading did as expected nothave any impact on disk performance. Disk benchmarks were also executed, but detailed results are not included due to the variability in IO systems:. All CPU and memory benchmarks have been included. “Preferences > Number of processes” set to number of logical processors on host (i.e. Mainly CPU and thread communication limited. IO-APIC, 100% Execution Cap, PAE/NX, VT-X / AMD-V, Nested Paging all enabledįor my particular requirements, I chose mainly multi-threaded CPU and memory bound benchmarks, with some disk benchmarks to guard against IO regressions – do follow the links for specifics on the individual benchmarks: y-cruncher #Virtualbox 64 bit not available amd cpu windows
Windows Server 2008 R2 Standard SP1 64-bit Note: The results in this article are likely notapplicable to NUMA systems with physical processors in multiple sockets, since these have very different memory, cache, and thread scheduling characteristics.
Note: All cores run at 3.7GHz during multi-threaded benchmarks for single-threaded benchmarks, the core runs between 3.7 and 3.9GHz. 
Single Intel Core i7 4770K, 3.5GHz, 4 physical cores, 8 logical cores (when Hyper-Threading is enabled) Physical Hostĭesktop system where the CPU and motherboard were released in AD 2013: CPU VirtualBox warns if the guest is configured with more processors than there are physical cores on the hostĪs always, these results are only valid for my particular configuration and on my chosen benchmarks, including the assumptions that the physical host is idling while the single virtual machine is running flat out – do test with your own systems and tasks.
0 kommentar(er)
