Problem - Activating SVM leads to significant BCLK variations
Problem - Activating SVM leads to significant BCLK variations
Hyper-V is turned off, just using Sandbox as a VM with a clean Windows setup. It seems enabling Sandbox automatically activates the hypervisor. The performance drop isn’t huge, but after spending time adjusting memory settings and running tests, this really reduces the value. My CPU now runs at 4450MHz instead of 4550MHz, Infinity Fabric is at 1866MHz instead of 1900MHz, and DRAM speed is 3733MT/s versus 3800MT/s. Even without launching it, having Sandbox enabled in Windows makes it easy to run when needed. If this only happens once I open the VM, I’d be fine, but most of the time I don’t use it. It’s handy to have it available when required.
This situation is really annoying. I plan to bring it up to the Sandbox community and Windows support for their insights. At the moment, my main concern is that a small amount of resources are being used by the program on the host machine, which might indicate a bug affecting only high-end users. Do you know if the sandbox runs on X86 or X64?