How long should I run each test before changing to the next value?
If if fails in a few seconds (20) you should try another value. If it unlocks in a few minutes, might be good enough. You get warnings in the window when the card enters LHR, mode, then the program will reset the lhr and this takes time and hurt the pool hashrate.
|
|
|
Any recommendation for a xitensity value on the LHR cards as a starting point?
If it fails to unlock at 1 reduce to -1, -2 etc. If it unlocks stable at 1 increase the number to 2, 3,4 to increase the speed. LHR cards are tricky, and takes a while to find the correct clock setting / LHR setting.
|
|
|
Should I try negative values this time?
Yes negative values are supported. The LHR docs are not updated to the later version. My GTX 3070 LHR works best with -4. 60% tdp, 7900Memory/ stable at 44MHASH . I use --log in the batfile
|
|
|
Can you suggest a kernel for full AMD rigs? It seems that autotune always select kernel 0.
v1.42 only have one active kernel for AMD About Hiveon pool rejected shares are always a problem, 1/2% average (tried xintensity 71 and 24), while they are close to zero in crazypool or 2miners for example
It used to be higher. We tried to improve it, but it keeps coming back. The hiveon pool have 0% fee, so even with 0.5% rejected you should get more shares than on the other pools you listed. The hiveon pool is using the ETHPROXY protocol and different code in the miner than the 2miners and crazypool.
|
|
|
video cards do not throttle, core frequencies do not drop off, this is out of the question. raising the power does not give an increase in hashrate, ethereum mining does not need a high core value, it only uses memory.
Some of your cards are not clocked correct, and some have fluctating power.
|
|
|
In Hive OS, it always sets kernel 1 automatically
Make sure that -J 1 is not passed. The program should autotune, or you can set -J -1 to force autotune. I tried kernels from 5 to 8 - they work poorly, very few shares are found.
On windows and cuda 11.5 kernel 5-8 gives the best results on RTX cards. The next version will have 16 kernels to try to improve the performance on low power. You need to find out why your cards in the rig is using 168- 241 watt. Cards seems to trottle. (downclock and perform poorly) They need to run at the same wattage all the time. Did you manage to run them in p0 state? v1.42 windows 11.5 build Kernel 1 RTX 2060 31 MHASH Kernel 8 RTX 2060 33.5MHASH (but needs more power) v1.43 will be released in a few hours.
|
|
|
I'm not familiar with how the LHR unlock works, but I am curious about how the lhr-unlock and the tweak settings work together.. Also, I assume that the intensity at -2 on the 3080's means something different than it does on the non-LHR cards, and the kernel selection for the 3080s being low values is also an LHR thing??
In the LHR more tweak will increase the load sent to the gpu since xintensity is not supported. It has a different meaning than in standard mode. In standard mode tweak will split jobs in order try to remove stale shares. This is not needed on the 2miners pool.
|
|
|
Added 2x 3080 LHRs to my setup and was hoping to get a stable hash rate on the cards. Any tips or options to add as a starting point?
On windows I use 75% powerlimit and low coreclock as possible on the 3080ti. No need to lock the clock. If the card fail to unlock try with -1, -2, -3, -4 ... etc until it's stable. --lhr-unlock [-1,-1,0,0,0,0]
|
|
|
You are locking the coreclock at 1250, you probolby need to increase it to 1500 or something. The watt on the card is unstable which indicate trottleing. The memory temp could be too high or power too low.
|
|
|
After 2 minutes, the hashrate dropped again, but still more than cuda 11.5 with 13 cards you should get at least 1.404GHASH in the miner window on optimal settings. 108MHASH each. But perhaps you are running in powersaver mode.
|
|
|
Cuda 11.4 RTX 3080 110.5mh
Now you need to find the correct intensity for your rig so that the mining speed is reflected poolside. When you are done you will understand why alot of miners have switched. AMD/NVIDIA. Try to combine high --xintenity with --tweak --kernel . The defaults will probably not work optimal.
|
|
|
I tried on 2miners , on a 12x3080 rig, Hive OS cuda 11.5 driver 495.46 cuda 8 xint 3108 , I have 1321mh in the miner window. Average per pool per day 1.24 ghs. It works well for the first hour, then it starts to fall behind. I can put it for you again for a test for a day, so that you can be convinced of this yourself. Maby in hive i must use 11.4 cuda , i dont know, but it not work ....
Try v1.42 cuda v11.4 build. 11.5 might have issues. As reported in the previous post. 3108 might not be the optimal config for your rig. This setting works good on 1 rtx 3090.
|
|
|
I spent about 4 days on tests,
Which version did you test. Which mining pool did you test? Let it run for 5000 shares. TBM should be faster if you configure it correctly.. What speed are you getting in the miner window. Screenshots please.
|
|
|
I have bad eanglish , it's a secret? I want use you miner, but don't understand, core clock musbe low or higher? Now I use 1440 on hive , on g miner I use 1100
No he posted in a public thread on reddit. Memclock higher. I think he had modified the cooler on the memory so that it could be clocked higher. I am unable to find the post now. A few months back. But TBM works better on 2miners than on ezil.me. On 2miners you can use --xintensity 3000 to 5000 without stale shares or rejects. (every share payed).
|
|
|
What settings do u use , core clock and memory ? And kernel ?
The record result was posted by a reddit user, the clocks and settings are hidden in one of the Team Black Miner threads there. Pro miners rarely share their settings because they are the only one who will survive if the price continue to fall.
|
|
|
Hi why on auto tuning I always have cuda kern 1 ? on my 3080 no lhr rig .Maby I use bad settings ? 1440 fix core , 2450 memory , pl 240 . What settings I must use ? Hive os cuda 11.5 , tbm 1.42 xint 284 pool ezil me . maby you say what the best kernel for this card , and same like 3070 3060ti no lhr ? Kernel 1 is the best ? Or 8 the best ? For best result I must use high core or low , like 1100 ? On 3070-3080 ?
Low kernel number is usually better if you run on low power settings, or if the card trottle. The autotune is running when the card is cold. You can let the rig run for 30mins, and restart the miner. Does it still end up on 1? Only way to do a better accurate measure is to let it run for a longer period of time. The RTX 3080 can do up to 111MHASH poolside on the 2miners pool on high --xintensity (100% mem usage / copyspeed
|
|
|
The 2060S is hashing at 40 MH/s but the client is reporting 44.75 (after 1 hour, so luck might be heavily influencing the result); do you know of any reason why utilization would be so low for the 2060S?
Normal for this card, but your hashrate is low. You should get around 47MHASH. My rtx 2060 laptop is at 88% utilization. Perhaps run with --lock-cclock [1250,1250] or similar can help. Try 1050 core, and 8100 memory. The 2060S can do more than 48MHASH with the Team Black Miner, but 46.5 with 95 Watt is better. Windows cuda 11_5 build core: 1050 mem: 8100 tdp: 60% --xintensity 512 --kernel 8
|
|
|
Nope. My 472.84 desktop driver is most stable. Tried another and got more rejects and stales. So I'll stay with it. Good luck
I included a cuda 11.4 build in v1.42. It's abit slower than 11.5 on the latest driver, but perhaps work good on your driver. Stales can be removed by reducing the default --xintensity
|
|
|
The 2060S can do more than 48MHASH with the Team Black Miner, but 46.5 with 95 Watt is better. Windows cuda 11_5 build core: 1080 mem: 8100 --xintensity 512 --kernel 8
|
|
|
|