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

on 2miners.com:

You will get rejected share (stale) if they don't pay for it . But in your screen you had 100% accepted so all good

Has nothing to do here, because teamblackminer is a stale share miner BY DESIGN   

Yeah stale share miner for AMD, on my Nvidia Testrigs i got 0 stale shares over 3 weeks of mining. Strange miner

This is from 2miners website, it is on the "shares" tab:

Recorded shares in the recent 6 hours are displayed in the table above. If you have a significant amount of invalid shares, please check the GPU overclocking settings of your mining rig. If there are many stale shares (more than 5% of all shares), there is an issue with your internet connection. We recommend you to ping the pool with a special stratum-ping tool. When rewards are distributed according to the PPLNS scheme invalid and stale shares are not credited.

The third column is estimated stale shares.
2miners pay for level 1 stales so it shouldn't be a problem. you have 100% accepted shares in the window. You can check in the pool statistics for stale shares.

Are you using --dagintensity in the batfile? Please try v1.37

[/quote]

Hello,

I am not using --dagintensity in the bat file.

I am now in 2miners and v1.37 and this is how it looks like:

00:01:03 [2022-01-10 12:20:25.282] eth.2miners.com (ethash)    PING: 200ms    DIFFICULTY: 2.03     EPOCH: 465
00:01:03 [2022-01-10 12:20:25.282]
00:01:03 [2022-01-10 12:20:25.282]
00:01:03 [2022-01-10 12:20:25.282] ID      BOARD    TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT
00:01:03 [2022-01-10 12:20:25.282] GPU0    590S     OpenCL  0       512     40/0    74      1200    2100    84
00:01:03 [2022-01-10 12:20:25.282] GPU1    6800     OpenCL  0       512     0/0     0       0       0       0
00:01:03 [2022-01-10 12:20:25.282] GPU2    1660S    CUDA    2       284     59/0    60      1034    7693    65
00:01:03 [2022-01-10 12:20:25.282] GPU3    1660S    CUDA    2       284     51/0    60      1031    7693    80
00:01:03 [2022-01-10 12:20:25.282] GPU4    1660S    CUDA    2       284     54/0    60      1034    7593    74
00:01:03 [2022-01-10 12:20:25.282]                                                                          303
00:01:03 [2022-01-10 12:20:25.282]
00:01:03 [2022-01-10 12:20:25.282] ID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE
00:01:03 [2022-01-10 12:20:25.282] GPU0    590S     351.37 kH/W   29.52 MH/s    28.97 MH/s    10/0/7       100.00%
00:01:03 [2022-01-10 12:20:25.282] GPU1    6800     0.00 H/W      63.89 MH/s    63.29 MH/s    27/0/12      100.00%
00:01:03 [2022-01-10 12:20:25.282] GPU2    1660S    467.83 kH/W   31.34 MH/s    31.62 MH/s    22/0/0       100.00%
00:01:03 [2022-01-10 12:20:25.282] GPU3    1660S    428.15 kH/W   34.68 MH/s    34.68 MH/s    10/0/0       100.00%
00:01:03 [2022-01-10 12:20:25.282] GPU4    1660S    456.16 kH/W   34.21 MH/s    34.21 MH/s    19/0/0       100.00%
00:01:03 [2022-01-10 12:20:25.282]                  340.70 kH/W   193.64 MH/s   192.76 MH/s   88/0/19      100.00%


Amd cards are not performing well, too many "malformed shares" =19 (not sure if the are called malformed).

Any suggestions are welcome

hello sp_ I think you should check why versions from 1.29 are slower with 3080 NON LHR cards, I have tried with all the tweaks, kernels and intensities suggested in the thread and it is impossible for me to reach the same speeds as 1.27.

I will continue to use that version as long as it is not outmatched by any other miner and for now, the difference is still more than 4%.

Thanks again for your hard work.

The speed is good. The miner window will report stale shares, but if you check the pool you will se almost no stales.

Thank you. Mining at 2miners

---

High xintensity only work on some pools. Pools that pay for stale shares. (f.ex 2miners.com, miningpoolhub, nanopool, f2pool and many others.)
The Ethereum blockchain reward stale work, and pools that are made for Bitcoin style blockchains doesn't work so good with the TBM miner.

High intensity with tweak might reduce the stales.

You can try 2miners.com with --xintensity 4096, and get 100% accepted shares and few stales poolside, but on flexpool, ethermine, crazypool.  ~5% stales and lower payouts.


512 AMD intensity is equal to 2048 for cuda cards. Above 1024 is probobly not working good on AMD cards, but I have reports of good returns with 6xxx on nvidia as well. On the 2080 Super. So perhaps 1250 is the maximum good value?

Thank you. Any more ideas for intensity or maybe more tweaks? It's already like sport for me - just wanna understand TBM! 

If no --kernel parameter is set the program will autotune automatically.

Here in the picture (RTX 2060 mobile on ubuntu 20.04) kernel 8 was selected and kernel 0 was measured to be 2.12% slower.  (gpu speed is percent of the fastest kernel)

On 1070 --kernel 0, 1 or 2 is usually the fastest. You need a high coreclock and power to get the best speeds.

Getting better results with GMiner - lower displayed hashrate but twice more shares per minute. But anyways I want to tweak TBM for my needs. EVGA 1070 FTW2

I would think that kern 6-8 will perform best.
but depends on the power settings of your gpu. A lower kernel number  works better if the gpu has a low tdp. Run the autotune a few times and see which one is the fastest in your setup. Increase the power if it doesn't end up 5-8

What kernel and tweak I must use for this cards ? 7-8 ? Or use only kernel without tweak ? Version tbm 1.35

try

--xintensity 3108

or

--xintensity 2331

And let it run for a few days.

Hi what settings I must use on rig with 13 3080 Palit GameRock no lh , I try any kernels and xint , but L0L miner , faster all time . I am on 2miners pool , driver 495.46 HIVE os , maby I don't understand what to do with alot of settings , kernel , tweak , xint . Can you help me ? I have the same rig , on lol , and it faster (((

v1.37

1. Fix shares per minute calculation.
2. Fix invalid shares after re-connecting to pool. (crazypool.org, 2miners.com and perhaps others)
3. Improve dag creation parallelization on nvidia multicard rigs.
4. Fix dagintensity to not crash on P104
5. Removed invalid shares on the hiveon pool.

linux later

https://github.com/sp-hash/TeamBlackMiner/releases

TeamBlackMiner_1_37_cuda_11_5.7z
https://www.virustotal.com/gui/file/1645aa64386044e32827d0a7aba54d8fabb57a6f98c7b6db858bc8ddb730425b?nocache=1

TeamBlackMiner_1_37_cuda_11_4.7z
https://www.virustotal.com/gui/file/8d7d1de5749682d40af9acffa3556581fcfb48a1ac73b9f76f4501062fe6dac7?nocache=1

TeamBlackMiner_1_37_cuda_11_3.7z
https://www.virustotal.com/gui/file/da6785846456fc1ee9aaac9c512c8102c664ba5696ce5605d453fa69abb99f8c?nocache=1

TeamBlackMiner_1_37_Ubuntu_20_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/0d16a6d23119883afc746ae748da27e677a75766079cead33477cdd82eaf7f0e?nocache=1

---------------------------



Are you using --dagintensity in the batfile? Please try v1.37


Cuda 11.3 build to the rtx 3060 owners (470.05 driver). Abit faster than 11.2 check it out.

The Poolspeed is sometimes high and sometimes low in the beginning. The average hashrate is only accurate after enough samples has been collected. The gpu can also trottle. f.ex if the memory or core is too hot, the speed will be reduced. Other factors that can reduce the poolspeed hashrate is problems with the internet / network / pool.

I see, so the reported hashrate should now be more accurate, right? However, why does the latest version show higher hashrate in the beginning and then it drops?

You should run the cuda 11.5 build for the best speed.

hashrate bugs in 1.28

When a solution was found,  it exited the solver immediately without scanning the whole range of nonces, but the full hashrate was added. This is caused a inflated hashrate. Worse on on low difficulty.
An index bug sometimes caused hash to be added to the wrong gpu, so if you run with a good gpu and a poor gpu in the rig, the poor gpu's hashrate could be inflated.

In 1.29 we don't send shares to the pool if the diff hash changed. On a vardiff pools (p2p style) or simulator pools this might reduce the hashrate, but we did it to reduce rejected shares on real pools like Nicehash.

in v1.36 we have increased the number of samples in the average hashrate, so you should run for a longer period of time.
We reduced the default intensity to reduce the stale shares.

Poolside the cuda_11_5 1.36 should be better, but the defaults might not.

f.ex for AMD cards
--xintensity 512 is pretty good on 2miners.com . Much better than 24.

AMD 6900xt:

xintensity 24: ~60MHASH poolside
xintensity 512: ~70MHASH poolside