Closed MoneroOcean closed 5 years ago
Please show result of full hashrate report, h
key, I will try simulate this issue later.
Thank you.
Will try to catch that during interactive session next time. Output above is from systemd based miner, so I can not press h
there unfortunately.
In this case hashrate report from API is fine too.
I successfully reproduced the bug, not all threads mine after fast dataset change, no extra information required. Thank you.
Thank you! Just in case just got this h output with bug:
[2019-10-01 01:30:13.577] speed 10s/60s/15m 1540.7 1540.5 1540.3 H/s max 6096.3 H/s
| CPU # | AFFINITY | 10s H/s | 60s H/s | 15m H/s |
| 0 | 0 | n/a | n/a | n/a |
| 1 | 1 | n/a | n/a | n/a |
| 2 | 2 | n/a | n/a | n/a |
| 3 | 3 | n/a | n/a | n/a |
| 4 | 4 | n/a | n/a | n/a |
| 5 | 5 | n/a | n/a | n/a |
| 6 | 6 | n/a | n/a | n/a |
| 7 | 7 | n/a | n/a | n/a |
| 8 | 8 | n/a | n/a | n/a |
| 9 | 9 | n/a | n/a | n/a |
| 10 | 10 | 770.3 | 770.2 | 770.0 |
| 11 | 11 | 769.9 | 770.6 | 770.3 |
| - | - | 1540.2 | 1540.8 | 1540.4 |
[2019-10-01 01:31:02.977] speed 10s/60s/15m 1540.2 1540.8 1540.4 H/s max 6096.3 H/s
Fixed, but I think pool should not do fast randomx switching, dataset re-initialization take some time. Thank you.
Thank you very much! Unfortunately sometimes it is inevitable in case of coin daemon having issues.
Thanks!
After fast algo switch (reproduced with rx/wow and rx/loki) sometimes 4.2.0-beta miner (saw it on all older v4 versions as well) starts to mine rx/loki with very low speed (6100 is expected, but it mines with 700 here). After next algo switch this is usually is fixed automatically: