Open Big-Daddio opened 3 years ago
As a workaround, it does work properly when put into config.json
... for now
Just case anyone else is looking, I ended up working around the problem by following the xmrig command line with this
wmic process where name="xmrig.exe" CALL setpriority "idle"
HTH
Also --cpu-priority
allegedly never works unless it's literally the last option on the command line (move it to the end).
Describe the bug cpu-priority not being honored on Windows 10 via command line - happening since 6.12 branch, 6.10 is OK
To Reproduce .\miners\XMRig_MO\6.12.2\xmrig.exe --asm=auto --donate-level=1 -t 0 --cpu-priority=0 -o stratum+tcp://gulf.moneroocean.stream:10008 -u xxx -p Lappy
Expected behavior Task manager priority should show as low when started with cpu priority 0, however it starts with normal priority every time
Required data
Additional context might be this issue https://github.com/xmrig/xmrig/issues/2351?_pjax=%23js-repo-pjax-container