While individual algorithm implementations are a bit unoptimized, XMRig achieves higher hashrates by employing better auto-config and more fine-grained thread scheduling: it can calculate a single batch of hashes using 2 threads for parts that don’t require much cache. For example, on a typical Intel CPU (2 MB cache per core) it will use 1 thread per core for cn/fast, and 2 threads per core for other Cryptonight variants while calculating the same batch of hashes, always achieving more than 50% CPU load.
For the same reason, XMRig can sometimes use less than 100% CPU on Ryzen 3000/5000 CPUs if it finds that running 1 thread per core is faster for some Cryptonight variants on your system.
Looks like your on windows, im linux so no need for those configs but exitcode is defo caused by wrong config. Have u tried conf wizard to create conf file…
Hope u get it working,looks like its nothing special compared to cpuminer tho,well i quess that it depends on what cpu you run. Sorry that couldnt help…Good luck
Managed to solve it.
The issue was not with the configurations,but something probably got stuck in the HiveOS configs.
I created a new flight sheet ONLY for Raptoreum using XMRig, it started successfully and then updated the same flight sheet by adding the ETH miner and restarted it. @Minercold you should try this as well I think.
I ran into the problem. Seems to happen if you’ve never run XMRIG before. I made a quick flight sheet to mine monero with xmrig then program started up fine. Then changed flightsheet to mine RTM
Trying a switch from cpuminer-opt to xmrig-new. Why does it only use 6 cores and doesn’t post the 12 threads like cpuminer-opt does? Is it still using all threads? Are there some config settings that could be shared please. Thank you all.
