search

Lolliedieb / lolMiner-releases

2.55k stars 575 forks source link

1.34 Win 10 lhr triggered, lhrtune down by -1 #841

Open MinerTi opened 2 years ago

MinerTi commented 2 years ago

It is possible to get lhrtune arg back to preview high by auto for example after 1 min. Gpu worked stable for 24h with --lhrtune in command line, then get -1 and now working with that value. Pls make --lhrtune to work auto in both side not only in "-" but and to "+" after lhr triggered.

jgonzis commented 2 years ago

It is possible to get lhrtune arg back to preview high by auto for example after 1 min. Gpu worked stable for 24h with --lhrtune in command line, then get -1 and now working with that value. Pls make --lhrtune to work auto in both side not only in "-" but and to "+" after lhr triggered.

It is automaticly done by the detection... if goes up +1 then it will get locked the GPU... so it detects best performance. Another thing is that you use also your computer meanwhile you are mining that will lock probably lot more time the GPU, but that is normal in LHR

MinerTi commented 2 years ago

Thx for fast answers. When mining pc not using, monitor fast off after lolminer started. Last night tried with --lhrtune +5, worked stable, rig speed 248 -> 250. Now trying rocket tune +20 :), rig speed 255.5. Thx for you hard work, waiting for next improvement.

MinerTi commented 2 years ago

Little update, --lhrtune +20, uptime about 8h, stable hashrate 255.5. Its went up from about 248 with --lhrtune without arg.

jgonzis commented 2 years ago

Little update, --lhrtune +20, uptime about 8h, stable hashrate 255.5. Its went up from about 248 with --lhrtune without arg.

1.35 will come with both tunning old 1.33 and new 1.34a for GDDR6X memory In ETH I hope you enjoy it

Lolliedieb commented 2 years ago

I will take all this as a feature request in direction of "only lower the value when the lock came too quick and / or check higher value when very long stable on the current one".

MinerTi commented 2 years ago

Yes, this is exactly for what I asked. Maybe add new --lhrtune-time. Default 0 - no feature, (1 - 60) minutes for checking stable work time.