Locked core clock speed is much better than power-limit, why is not included by default?

[mxm]

Great results. My FEs are not so good compared to ASUS:

Is it TUF or STRIX?

[DuleC]

TUF version. Try to play with core freq to find the sweet spot, it is quick.

Really great update, thanks for bringing this up :).

[mxm]

Yeah, I did play a few days with it. Sweet spot is on 1410 for my cards.

But I prefer combination of setting offset in GUI and manual core lock. That technique gives me the best results.
GUI only:

GUI offset + manual core lock on 670 (3070)/910 (3060ti):

[jgonzi]

At the end it is a good table information and optimal values for lolMiner last version… that will consume less Watts and reduce temps in memory.

Lolliedieb/lolMiner-releases

[danielvm]

I was trying to set the offset automatically but it seems impossible

How to run a command with the boot

Sleep is in seconds I think. It’s annoying that you cannot script easily a simple command given how powerful and configurable HiveOS is. If I don’t lock the gpu clocks after boot, I get restarts (something to do with one of PSUs not liking the power spikes from GPUs clocking up).

[DediZones]

check forum

How to run a command with the boot

Hello, Try this: cd /opt mkdir script_dedi cd script_dedi nano xinit.dedi.sh Exemple for me: #!/usr/bin/env bash nvidia-smi -i 1,2,3,4,5 -lgc 900 press F3 “for write” or CTRL + S F2 “for quit” or CTRL + Q chmod +x xinit.dedi.sh After add in reboot or boot crontab nano /hive/etc/crontab.root and add this: @reboot sleep 900 && /opt/script_dedi/xinit.dedi.sh 900 in second / 15 min change with your value time press F3 “for write” or CTRL + S F2 “for quit” or CTRL + Q Test your s…

[flashgear]

So what is the general consensus for the 3070’s?

-400 core / nvidia-smi -i -lgc 690 (or higher?)

or

Locked Core 1065/1070ish?

[schtm]

An alternative, which I have been using is to set positve core offset and then use the -lgc command to fix the max core. In this way you are able to runt higher core clocks at lower volt. I am not sure if this is better but get similar result. This is what I use:
3070: +250, -lgc 1350
3060ti: -500, -lgc 925 (3060ti works different from 3070/3080 it seems…)
3080: +250, -lgc 1075 (this also works well to fix and ignore -lgc)

Comments and thoughts? Seems that power is a bit higher but is quite important if you mine something else than Etherum.

[danielvm]

I’m experiencing difficulties setting this way so I tried the 670 directly on the GUI and it looks fine, I’m getting the better efficiency I could see until now (besides less 2Mh/s on performance).

520kH/watt

I don’t know what is better, to run with 2 more Mh/s or to be more efficient in therms of kH/watt.

My previous setting was this one:

Locked core clock speed is much better than power-limit, why is not included by default?

I saw ChampChangeXD on youtube with this settings and give it a try [Screen Shot 2021-04-10 at 22.54.05] I also tried fixing the core on 900, 950, 1000, 1050, 1060 and found that the first number that make my system stable is 1070. pretty efficient as well [Screen Shot 2021-04-10 at 23.00.38]

[mxm]

Personally, I’d go for an extra 2Mh. You are losing 14Mh overall.
I’ve settled on -400, lgc 670 for my 3070s. Hashing well so far on 2550 MEM

Also I’ve put nvidia-smi commands in a script and set it as start script in T-rex with “script-start”:"/home/user/set-gpu-clock.sh"
Now it sets gpu clocks automatically every time I restart miner or reboot the rig and I don’t have to bother doing it manually.

[olcyy]

Could you give me more detail for how to make your script. That interests me a lot. Thank you !

[slvhiveos]

Similar. Better to set -offset and then from cli

eg, offset -500, cli 750, perfect result
If I enter directly 750 to web gui, results is 1.5-2mhs/per card lower

How it can be ?

[SnowmanSimon]

Wow tried this on my 2060. Core at 1000 and dropped watts from 125 to 68 and same 30.5mh. Wild!

[mxm]

@slvhiveos

How it can be ?

Effective GPU clocks = lgc value - offset value
In you first case Effective clocks = 750 - (-500) = 1250MHz, which is too much for 3070 and too low for 3060ti. For 3070 you shold aquire better results around 1080MHz effective GPU clock and for 3060ti - around 1425. But every silicon is different so YMMV.
When you enter 750 in GUI your offset =0, so
effective clock = 750 - 0 = 750 Mhz, hence lower hashrate.

It is strange, but setting offset -400 and lgc 680 gives 3-5W lower power consumption and the same hashrate compared to offset 0 and lgc 1080 (entering 1080 directly in the gui).
I’m suspecting that software wattmeter could be not correct in that specific case. I plan to test it with hardware wattmeter. It could be there is no difference in real power consumpion. Will check that theory when I get my hardware Kill-a-watt.

[flashgear]

How does your invalids go after doing this? And what’s your mem clocks?

[slvhiveos]

Thanks for deep answer
Yap, it seems there is difference in set gpu clock in one step or in 2 steps (gui + after cli)
I’ll test 1080MHz in gui vs -500 gui at boot and 750 cli
or… eg -500 gui and after 1080MHz in gui too

Thanks a lot

[slvhiveos]

In my quick try… (4xRTX3070)
PL: 130

1. GUI 1250: Power (with cpu etc): 515W, HR: 252,2MHs
2. GUI -500 + CLI 750: Power (with cpu etc): 503W, HR: 252,1MHs

Time waiting for stabilize ~> 1h
It’s seems it’s repeatable

[ajps1306]

any tips for Asus TUF OC 3080?

Thanks in advance

[j2h4u]

Good thing you don’t have to use sudo in the Hive console

[j2h4u]

Hope this ‘‘secret’’ config file will come in handy. You can create a skeleton version by executing

echo 'DEF_FIXCLOCK=-200' > /hive-config/busid.conf

and then forget about lgc thing for good