Topic: Team Black Miner (ETHW ETC Vertcoin Ravencoin Zilliqa +dual +tripple mining ) - page 57. (Read 35100 times)

run

$ tbminer --list-devices

Using 1.24 Ubuntu 18 :
OpenCL driver version: 470.82
00:00:00 [2021-11-12 22:43:26.417] Cuda driver version: 11.4
00:00:00 [2021-11-12 22:43:26.417] Cuda runtime API version: 11.4

terminate called after throwing an instance of 'cuda_runtime_error'
terminate called recursively
terminate called recursively
terminate called recursively
Aborted (core dumped)

Going to try updating drivers

Edit: Getting closer?
00:00:00 [2021-11-12 23:04:31.759] OpenCL driver version: 495.29
00:00:00 [2021-11-12 23:04:31.843] Cuda driver version: 11.5
00:00:00 [2021-11-12 23:04:31.843] Cuda runtime API version: 11.5


terminate called after throwing an instance of 'cuda_runtime_error'
  what():  CUDA error in func set_constants at line 925 invalid device symbol
Aborted (core dumped)

Not sure what to do, T-rex and others working but I wanna go faster

The next version will have a --timeout option so you can mine for xxx minutes. Then you can create a script to find the optimal intensity setting for the pool.

Are there any settings I can modify to increase the number of submitted accepted shares on 2Miners?

On the 1080ti Kernel 0 is better with low power, but you have power. Perhaps you can add --kernel 8 to get back the 1mhash. Overall your setting looks good.
The pool share and the Pool Hashrate:picture  doen't seem to match the miner output though. Only 549 shares, but 1 894 shares total in the other pictures.


edit: 2miners only show the last 6 hours. in the stats.

TBM 1.24

My 15hrs mining report.

6800XT and 1080Ti:
https://i.imgur.com/rl8nTC6.jpg

3090 and 3070:
https://i.imgur.com/rFg801W.jpg

Pool Share:
https://i.imgur.com/Y7AV0oL.jpg

Pool Hashrate:
https://i.imgur.com/D8SByMj.jpg

Initially there was one stale share reported from 3090, then I reduced overclock (Loss of 1mh/s) after that no stale. All good with respective xintensity.
But somehow my 1080Ti is not performing well here as compared to previous (48Mh/s). (Was using v1.23 with kernel 8 )
Anything more to do now or is it all good?  

Thanks for your support the work on the LHR is progressing, but Nvidia will probobly release LHR3 and then the work could be wasted. Better to increase the speed on AMD cards. I expect a nice surprise for 6800xt and 6900xt owners soon. Perhaps a X-mas gift from the TBM team.

I get 0 stale shares reported.

So 0.5% is lost

There was another user who got a good result with --xintensity 3108 on a single rtx 3090, perhaps 4096 is too high for this pool.

Yes I have only 1

Worker   Valid Shares   Invalid Shares   Stale Shares   Last Share
Total   202   0 (0%)   1 (0%)   28 seconds ago
RTX3080   160   0 (0%)   1 (0%)   a minute ago
RX5500XT   42   0 (0%)   0 (0%)   28 seconds ago

Thanks for your support. In the next version we are recoding the AMDstats code so that you can get temps, and clocks of the gpu on linux. We are also going to add mining in the dag verification phrase that will add a few seconds of mining on every dag change.

---

Only if you get stale shares. Click on the worker on the pool and check for stales



[moderator's note: consecutive posts merged]

Worker   Valid Shares   Invalid Shares   Stale Shares   Last Share
Total   202   0 (0%)   1 (0%)   28 seconds ago
RTX3080   160   0 (0%)   1 (0%)   a minute ago
RX5500XT   42   0 (0%)   0 (0%)   28 seconds ago

RTX3080: --xintensity 4096
RX5500XT: --xintensity 256

After 14 hours:

RX5500XT: pool hashrate 26.59 / average reported 28.07 = 94.82%
RTX3080: pool hashrate 95.17 / average reported 101.32 = 93.93%

Do you think that with lower --xintensity I have better pool hashrate?

Thank you!

Do you get any stale shares on 2miners with --xintensity 4096?

I am getting 3% more accepted shares plus the additional 13% stale shares on TBM 1.24 compared to TBM 1.23.

TBM 1.23
--xintensity 1024
--dagintensity 9
--kernel 0

   360m [2021-11-10 23:51:35.412] us-eth.2miners.com (ethash)    PING: 67ms    DIFFICULTY: 2.03     EPOCH: 453                                                                           
   360m [2021-11-10 23:51:35.412]
   360m [2021-11-10 23:51:35.412] ID        BOARD    TYPE    KERN   XINT    TEMP   FAN    CORE   MEM     WATT   
   360m [2021-11-10 23:51:35.412] GPU0    3060Ti    CUDA    4        1024    64/0    70      1415    8067    155   
   360m [2021-11-10 23:51:35.412] GPU1    3060Ti    CUDA    8        1024    74/0    79      1527    8067    175   
   360m [2021-11-10 23:51:35.412] GPU2    3060Ti    CUDA    5        1024    70/0    70      1427    8067    155   
   360m [2021-11-10 23:51:35.412] GPU3    3060Ti    CUDA    5        1024    64/0    79      1593    8067    184   
   360m [2021-11-10 23:51:35.412] GPU4    3060Ti    CUDA    8        1024    68/0    70      1486    8067    155   
   360m [2021-11-10 23:51:35.412] GPU5    3060Ti    CUDA    4        1024    63/0    70      1452    8067    155   
   360m [2021-11-10 23:51:35.412]                                                                                                       979   
   360m [2021-11-10 23:51:35.412]
   360m [2021-11-10 23:51:35.412] ID        BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES     RATE   
   360m [2021-11-10 23:51:35.412] GPU0    3060Ti   419.30 kH/W      64.99 MH/s    64.97 MH/s    141/1/0      99.30% 
   360m [2021-11-10 23:51:35.412] GPU1    3060Ti   371.26 kH/W      64.97 MH/s    64.95 MH/s    159/0/0      100.00%
   360m [2021-11-10 23:51:35.412] GPU2    3060Ti   419.21 kH/W      64.98 MH/s    64.96 MH/s    150/0/0      100.00%
   360m [2021-11-10 23:51:35.412] GPU3    3060Ti   353.11 kH/W      64.97 MH/s    64.95 MH/s    147/0/0      100.00%
   360m [2021-11-10 23:51:35.412] GPU4    3060Ti   419.20 kH/W      64.98 MH/s    64.95 MH/s    153/0/0      100.00%
   360m [2021-11-10 23:51:35.412] GPU5    3060Ti   419.26 kH/W      64.99 MH/s    64.97 MH/s    170/0/0      100.00%
   360m [2021-11-10 23:51:35.412]                           400.23 kH/W   389.88 MH/s   389.76 MH/s   920/1/0 99.89% 
   360m [2021-11-10 23:51:35.412]                                                                                 
   360m [2021-11-10 23:51:35.412] SHARES PER MINUTE: 2.56            POOL HASHRATE: 372.70 MH/s

TBM 1.24
--xitensity 4096
--dagintensity 9
--kernel 0

00:06:01 [2021-11-11 20:24:58.443] us-eth.2miners.com (ethash)    PING: 68ms    DIFFICULTY: 2.03     EPOCH: 453
00:06:01 [2021-11-11 20:24:58.443]                                                                                 
00:06:01 [2021-11-11 20:24:58.443] ID         BOARD    TYPE    KERN    XINT    TEMP   FAN   CORE  MEM   WATT   
00:06:01 [2021-11-11 20:24:58.443] GPU0    3060Ti    CUDA    7          4096    63/0    70      1417    8067    155   
00:06:01 [2021-11-11 20:24:58.443] GPU1    3060Ti    CUDA    4          4096    64/0    79      1593    8067    184   
00:06:01 [2021-11-11 20:24:58.443] GPU2    3060Ti    CUDA    5          4096    68/0    70      1437    8067    155   
00:06:01 [2021-11-11 20:24:58.443] GPU3    3060Ti    CUDA    4          4096    57/0    79      1633    8067    183   
00:06:01 [2021-11-11 20:24:58.443] GPU4    3060Ti    CUDA    8          4096    66/0    70      1496    8067    155   
00:06:01 [2021-11-11 20:24:58.443] GPU5    3060Ti    CUDA    6          4096    62/0    70      1464    8067    155   
00:06:01 [2021-11-11 20:24:58.443]                                                                                                         987
   
00:06:01 [2021-11-11 20:24:58.443] ID         BOARD    HASHRATE/W    HASHRATE   AVERAGE       SHARES       RATE   
00:06:01 [2021-11-11 20:24:58.443] GPU0    3060Ti   419.57 kH/W   65.03 MH/s    65.03 MH/s    158/0/22     100.00%
00:06:01 [2021-11-11 20:24:58.443] GPU1    3060Ti   353.34 kH/W   65.01 MH/s    65.02 MH/s    152/0/13     100.00%
00:06:01 [2021-11-11 20:24:58.443] GPU2    3060Ti   419.54 kH/W   65.03 MH/s    65.03 MH/s    160/0/21     100.00%
00:06:01 [2021-11-11 20:24:58.443] GPU3    3060Ti   355.25 kH/W   65.01 MH/s    65.02 MH/s    153/0/23     100.00%
00:06:01 [2021-11-11 20:24:58.443] GPU4    3060Ti   419.52 kH/W   65.03 MH/s    65.02 MH/s    166/0/25     100.00%
00:06:01 [2021-11-11 20:24:58.443] GPU5    3060Ti   419.56 kH/W   65.03 MH/s    65.03 MH/s    157/0/19     100.00%
00:06:01 [2021-11-11 20:24:58.443]                          397.80 kH/W  390.15 MH/s   390.15 MH/s   946/0/123 100.00%
00:06:01 [2021-11-11 20:24:58.443]                                                                                 
00:06:01 [2021-11-11 20:24:58.443] SHARES PER MINUTE: 2.63            POOL HASHRATE: 382.17 MH/s

The xintensity setting is definitely allowing me to gain more accepted shares compared to what I was using before.

PLEASE KEEP UP THE GREAT WORK!!!!!!

---

Here is a screenshot of current mining results on localhost running TBM 1.24:



And another screenshot of the worker current/average/reported hashrate on 2Miners:







[moderator's note: consecutive posts merged]

Chinese miners seem to be smarter than the american miners...  



live dev fee@teamblack...

Same picture at 2miners. 1.23 is better for me. Thank you for your help!

We had the same problem for nvidia but it is fixed now, the dag validation is not supposed to add hashrate. Will take a look in the opencl code as well. 

---

The --xintensity setting is important in the tbminer. If you set it wrong you get -5%, set it right you can get 5%. The setting is pool dependent. There is no optimal intensity for all pools...
Important bugs on some pools have been fixed in 1.24 and users are adviced to upgrade...

[moderator's note: consecutive posts merged]

It seems like the "Average Hash Rate" reported by the client is overly sensitive to high initial hash rates and in HiveOS is causing a significant mis-reporting of the miner hashrate.

For example, on startup I might see some hashrate like 94, or 114 for my AMD 6X00 cards and within a couple of minutes, the true hash rate has decreased to a stable hashing speed, however those initial readings keep the HiveOS reported rates much higher than what the client is actually reporting.  Maybe the client can simply dispose of the first few samples after a few minutes and then capture the real average -- or capture the median or mode instead of the mean value?

Absolutely same settings: --kernel 0 --xintensity 600 --dagintensity 1

Superb... TBM ...cant wait for dev to crack down LHR..

already test 1.24 for 2H ....massive increase for me..

1.24

1.23

thank you dev...