However, when setting up more than 6 cores, VMWare gives a warning that this may negatively impact performance on both MacOS and the Guest OS. I just want it to run as effective as possible.My inclination is to set the VM to use 12 Cores so that each vCPU of the i7 is available to the guest. I don't mind if this impacts usability of host or guest while the workload is running. That said, let us find out which is the best Hypervisor for macOS and the virtualization programs that work well with macOS:I have a very CPU intensive and highly parallizable workload for Windows that I want to run and get the maximum out of the CPU.

However, since this will still be running for a couple of days I don't wan to get into a situation where it slows down later in the process due to some problem related to using too many cores.So the rule of thumb is no more than N-1 virtual (vmware) cores per any individual VM, where N is the number of physical (not virtual, not hyperthreading cores in the machine), and ideally no more than N-2 (so there's always 2 for the host).Hyperthreading is irrelevant in this case, it's physical cores - the details are somewhat arcane, but it has to do with how both the host and guest OS lock them during use. I'm not quite certain what to make of that.Initial test running the workload for some time show that it seems to perform better in the 12 cores setup. Is this just a general warning that I am allowing Windows to eat up all the CPU cycles while running my workload? Again, that wouldn't be a problem since I am looking to fully utilize the CPU anyways.I guess I'n not quite sure on how physical CPU cores and hyperthreading vCPUs are treated here and how the guest will be able to utilize the cores.When I set up the VM to use all 12 Cores and start my workload with 12 threads, I can see in the MacOS ActivityMonitore that all 12 vCPUs are being fully utilized.When I'm running the VM with 6 CPU cores and run with 12 Threads, I see only 6 CPUs fully utilized and the other 6 at 60%-75% utilization.

When hyperthreading is enabled, the two hyperthreads share the L1/L2 caches and execution engine. The execution engine is where all the actual CPU work gets done. The L1 has separate data cache and instruction cache. On a 4-core host, I wouldn't run more than one 2-core guest at a time if there's any significant load on the host.At a high level, each CPU core has its own L1/L2 caches and execution engine.

Strictly speaking OEM licence is not transferableI was actually able to use Clonezilla. You might have to reactivate the Windows licence and may have to justify it to Microsoft as the licence has already been activated for the VM I think this applies if the OS licence is Retail or OEM but maybe not for Enterprise licence. I think it is best just to go with the standard Apple Bootcamp process. While CPU virtualisation technology has vastly improved and made running VMs more efficient, there is still some unavoidable overhead of running a VM that will never be issue when compared to running Windows on the Mac mini natively.Playing devil's advocate, if you don't have a need to access the macOS while this workload is running, why not run this workload within Windows Bootcamp natively instead of as a VM?I am not aware of a procedure to convert a Windows VM into a Bootcamp partition. 2 core/4threads CPU cannot match a 4 core/4 thread CPU).In this situation with 12 vCPUs assigned to the VM, it is as close as it gets to have a 6 core/12 thread performance even though the Windows VM sees 12 virtual cores as the underlying hardware remains the same.

You can even bring it back in as a BootCamp VM in Fusion. After that, you can boot the cloned widows system like a BootCamp system. If it is an external drive, you may need to boot the mac to recovery mode and allow booting from external media. Use Clonezilla to clone windows.

Best Mac Vm For Windows