Hello, it turned out, that Windows 11 (and some newer versions of Windows 10) changed its way of reporting CPU cores, which is affecting the performance of V-Ray 5 Benchmark. We’ll soon release a fix for that. If you don’t want to wait until such a fix is released, there’s a workaround described on docs.microsoft.com, which involves executing the Powershell command reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NUMA" /v SplitLargeNodes /t REG_DWORD /d 1, and restarting your machine.
Applications that are updated to use the new API functionality that reports the true NUMA topology will continue to work properly on systems where large node splitting has been reenabled with this registry key.
So, the performance of applications, which are already working, should not be affected.
NO changes for me to reach linux, but now near from Win10. . Boot in linux same PBO level 2 = 68 541 . Boot in windows 11 = 56 773 . Near of Win10 but not so good as linux
When will it all be over already? Why can’t a huge, giant corporation code properly? What happened to the industry? Why has everything become so horribly badly coded? Speechless…