Open cbepxpa3ym opened 3 years ago
you have to let miner mines few hours (at least 6h, 8h or even 24h) before pool side's current or average hash tends to equal your local side's hash. then on the pool side, hash (current and or average) can sometimes still be below what your miner tells you (reported hash) but it also can be higher. this is the nature of mining. there is a so called luck factor. long story short, pplns pools works on an average base. as soon as you stop mining it can drastically lower your yield so better never stop or the least you can. just wait some times and all should be good.
My card is 3080 LHR. I run dual mining (ETH/ERGO) with lhr-tune 37 and auto tune turned off. Almost all the time it shows me 50 MH/s with ETH and 125 in ERGO. Sometimes jumps up to 60-70 MH/s, which techincally is not be possible even in solo mining of ETH. In the same time it shows max 33-40 MH/S in the pool stats of ETH. So, T-Rex shows wrong hashrate.
@cbepxpa3ym could you please run the miner with -N 180 --log-path trex.log
for a few hours until the miner starts reporting ~50MH on your 3080 LHR and upload the log file? Make sure you're using version 0.24.2. Thanks.
Looks like this happens when diff is too low. For example, with nicehash I get 250 M difficulty, so hashrate is 60 mh/s, even 70 mh/s sometimes... but sometimes it is 30 mh/s with the same diff. But with 8 G diff I did not get this issue on another pool. It shows 37 mh/s if lhr-tune is 37. Looks like you have some issue with math.
I see. So, could you please post the log file?
It reports 37-40 MH/s, but pools show around 20 MH/s. When it shows around 50-60 MH/s, pools show around 33 MH/s. I tried various pools.