MoneroOcean / xmrig

Monero (rx/0, rx/wow, rx/loki, defyx, rx/arq, rx/sfx, rx/keva, cn/0, cn/1, cn/2, cn/r, cn/fast, cn/half, cn/xao, cn/rto, cn/rwz, cn/zls, cn/double, cn/gpu, cn-lite/0, cn-lite/1, cn-heavy/0, cn-heavy/tube, cn-heavy/xhv, cn-pico, cn-pico/tlo, argon2/chukwa, argon2/wrkz, astrobwt) CPU/GPU miner
https://moneroocean.stream
GNU General Public License v3.0
271 stars 82 forks source link

MO xmrig doesn't use best algorithm #45

Open AnErrupTion opened 3 years ago

AnErrupTion commented 3 years ago

Describe the bug MO xmrig doesn't seem to use the best algorithm according to the results.

To Reproduce Not much steps to reproduce, however here's my CPU : Intel Pentium G3258 @ 3.20 GHz (stock speed)

Expected behavior It should have used the best algorithm based on the hashrate generated by the algorithms

Required data Screenshot of the two algorithms which performed the best on my hardware : Screenshot from 2021-04-04 15-31-59 It used the algorithm panthera, while rx/arq was clearly the best.

Configuration file : { "api": { "id": null, "worker-id": null }, "http": { "enabled": false, "host": "127.0.0.1", "port": 0, "access-token": null, "restricted": true }, "autosave": true, "background": false, "colors": true, "title": true, "randomx": { "init": -1, "init-avx2": 0, "mode": "auto", "1gb-pages": true, "rdmsr": true, "wrmsr": true, "cache_qos": false, "numa": true, "scratchpad_prefetch_mode": 1 }, "cpu": { "enabled": true, "huge-pages": true, "huge-pages-jit": true, "hw-aes": null, "priority": null, "memory-pool": true, "yield": true, "asm": true, "argon2-impl": null, "astrobwt-max-size": 550, "astrobwt-avx2": false, "argon2": [0, 1], "astrobwt": [0, 1], "cn": [ [1, 0], [1, 1] ], "cn-heavy": [ [1, 0] ], "cn-lite": [ [1, 0], [1, 1] ], "cn-pico": [ [2, 0], [2, 1] ], "cn/gpu": [0, 1], "panthera": [0, 1], "rx": [0, 1], "rx/wow": [0, 1], "cn/0": false, "cn-lite/0": false, "rx/arq": "rx/wow", "rx/keva": "rx/wow" }, "opencl": { "enabled": false, "cache": true, "loader": null, "platform": "AMD", "adl": true, "cn/0": false, "cn-lite/0": false, "panthera": false }, "cuda": { "enabled": false, "loader": null, "nvml": true, "cn/0": false, "cn-lite/0": false, "astrobwt": false, "panthera": false }, "log-file": null, "donate-level": 0, "donate-over-proxy": 1, "pools": [ { "algo": null, "coin": null, "url": "gulf.moneroocean.stream:10128", "user": "my_wallet", "pass": "x", "rig-id": null, "nicehash": false, "keepalive": true, "enabled": true, "tls": false, "tls-fingerprint": null, "daemon": false, "socks5": null, "self-select": null, "submit-to-origin": false } ], "retries": 5, "retry-pause": 5, "print-time": 60, "health-print-time": 60, "dmi": true, "syslog": false, "tls": { "enabled": false, "protocols": null, "cert": null, "cert_key": null, "ciphers": null, "ciphersuites": null, "dhparam": null }, "user-agent": null, "verbose": 0, "watch": true, "rebench-algo": false, "bench-algo-time": 20, "algo-perf": { "cn/1": 42.41658772760762, "cn/2": 42.41658772760762, "cn/r": 42.41658772760762, "cn/fast": 84.83317545521524, "cn/half": 84.83317545521524, "cn/xao": 42.41658772760762, "cn/rto": 42.41658772760762, "cn/rwz": 56.555450303476828, "cn/zls": 56.555450303476828, "cn/double": 21.20829386380381, "cn-lite/1": 119.77686559309547, "cn-heavy/0": 0.0, "cn-heavy/tube": 0.0, "cn-heavy/xhv": 12.731481481481481, "cn-pico": 509.6842105263158, "cn-pico/tlo": 509.6842105263158, "cn/ccx": 72.3081780865172, "cn/gpu": 8.104410062098726, "rx/0": 547.7794148600294, "rx/wow": 891.9174910545148, "rx/arq": 3511.8947368421056, "rx/sfx": 547.7794148600294, "rx/keva": 0.0, "argon2/chukwa": 0.0, "argon2/chukwav2": 883.8947368421053, "argon2/wrkz": 0.0, "astrobwt": 132.09135880433639, "panthera": 1230.3157894736842 }, "pause-on-battery": false, "pause-on-active": false }

OS: Linux (Arco Linux)

Additional context None

mreed911 commented 3 years ago

It uses the values to determine the most profitable. Just because it’s fastest doesn’t mean that coin is profitable. Your client feeds that data to the server and it decides what to tell your client to mine. You’ll see it switch as coin values change.

This is working as designed.

Spudz76 commented 3 years ago

hashrate comparison between algos means nothing. "one hash" is not equal between them. The coin served to you is the one that makes the most earnings at the current prices (hashrate * value). If the hashrate of a worthless coin is 1MH/s it still is worse to mine than something else that does 5H/s but is worth a billion dollars per token.

Another analogy, if someone gave you job paying 80000 pennies that is worse than a job paying 3500 quarters. But the pennies one is bigger quantity of coins...