Pages:
Author

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

sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
Reducing mem clock on 3070 did the trick.
I found this annoying bug: starting the miner, on some cards, it takes some time before showing the average hashrate.
Seeing some cards at 0MHs could trigger watchdog and reboot rig.

It won't trigger the watchdog. When you increase the intensity gpu samples take longer time to complete and the average is only calculated if you have enough samples. We could let the average be calcuted of the existing samples but then the speed will trottle in the beginning.
jr. member
Activity: 87
Merit: 5
Reducing mem clock on 3070 did the trick.
I found this annoying bug: starting the miner, on some cards, it takes some time before showing the average hashrate.
Seeing some cards at 0MHs could trigger watchdog and reboot rig.

https://ibb.co/vXJ3D6P

Is it possible to fix that?
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
reduce the clocks and or increase power on gpu4. --xintensity 1024 is fine with miningpoolhub. Stales are rewarded 100%, so stale count doesn't matter
jr. member
Activity: 87
Merit: 5
Testing Flexpool with xintensity 896:
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269] flexpool.io (ethash)    PING: 26ms    DIFFICULTY: 0.931    EPOCH: 446                                     

You are using port 4444 on flexpool which is 4GH if you use high intensity switch to port 14444 which is 100GH.
If not, you will get too many stale shares..

I switched to 100GH port but still got too many stales (xintensity at 1024 at the moment):

│[2021-10-12 09:37:06][info][miner/0]:     91m [2021-10-12 09:37:05.284] ID      BOARD   HASHRATE/W      HASHRATE        AVERAGE         SHARES                                                                   
│[2021-10-12 09:37:06][info][miner/0]:     91m [2021-10-12 09:37:05.284] GPU0   3080    453.35 kH/W     102.00 MH/s     102.30 MH/s     12/0/1 (100.00%)                                                           
│[2021-10-12 09:37:06][info][miner/0]:     91m [2021-10-12 09:37:05.284] GPU1   3080    457.05 kH/W     102.38 MH/s     102.36 MH/s     5/0/0 (100.00%)                                                           
│[2021-10-12 09:37:06][info][miner/0]:     91m [2021-10-12 09:37:05.284] GPU2   3080    465.35 kH/W     102.38 MH/s     102.36 MH/s     8/0/1 (100.00%)                                                           
│[2021-10-12 09:37:06][info][miner/0]:     91m [2021-10-12 09:37:05.284] GPU3   3080    455.02 kH/W     102.38 MH/s     102.36 MH/s     2/0/1 (100.00%)                                                           
│[2021-10-12 09:37:06][info][miner/0]:     91m [2021-10-12 09:37:05.284] GPU4   3080    463.25 kH/W     102.38 MH/s     102.36 MH/s     5/0/4 (100.00%)                                                           
│[2021-10-12 09:37:06][info][miner/0]:     91m [2021-10-12 09:37:05.284] GPU5   3080    476.15 kH/W     102.37 MH/s     102.36 MH/s     9/0/1 (100.00%)                                                           
│[2021-10-12 09:37:06][info][miner/0]:     91m [2021-10-12 09:37:05.284]              2770.18 kH/W    613.89 MH/s     614.11 MH/s     41/0/8 (100.00%)       

I'm thinking to try MiningPoolHub, is it OK to keep xintensity to 1024 for this pool?



Got a problem with one of my rigs (2x3070 + 4x3080)
Miner doesn't start with this errors:

│[2021-10-12 10:07:56][info][miner/0]:      0m [2021-10-12 10:07:55.279] GPU3 Dag buffer verified ok!                                                                                                           
│[2021-10-12 10:07:56][info][miner/0]:      0m [2021-10-12 10:07:55.281] GPU2 Dag buffer verified ok!                                                                                                           
│[2021-10-12 10:07:56][info][miner/0]:      0m [2021-10-12 10:07:55.293] GPU0 Dag buffer verified ok!                                                                                                           
│[2021-10-12 10:07:56][info][miner/0]:      0m [2021-10-12 10:07:55.293] GPU5 Dag buffer verified ok!                                                                                                           
│[2021-10-12 10:07:56][info][miner/0]:      0m [2021-10-12 10:07:55.769] GPU4 Dag verification failed. Exiting...                                                                                               
│[2021-10-12 10:07:56][info][miner/0]:      0m [2021-10-12 10:07:55.769] Shutting down threads                                                                                                                   
│[2021-10-12 10:07:56][info][miner/0]:      0m [2021-10-12 10:07:55.770] Stratum thread exited                                                                                                                   
│[2021-10-12 10:07:56][info][miner/0]:      0m [2021-10-12 10:07:55.778] GPU1 Dag verification failed. Exiting...       

Don't know what to do...

[moderator's note: consecutive posts merged]
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
Testing Flexpool with xintensity 896:
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269] flexpool.io (ethash)    PING: 26ms    DIFFICULTY: 0.931    EPOCH: 446                                     

You are using port 4444 on flexpool which is 4GH if you use high intensity switch to port 14444 which is 100GH.
If not, you will get too many stale shares..



When I start the miner I always got these warnings, is it normal?

Do you have 2 instances of the miner running on the same computer? Find the option to switch off the api, or change the api port





1-2 times 1.13 got lagging, so no new entry to see, gpu temp also show no mining because its cold. Press enter helped.

This is an issue in windows 10 if you mark text in the commandline window, the app will stop mining. f.ex by rightclicking in it.

Has nothing to do with the version number.



I suggest that you report issues on our github

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

4 open, 53 closed.


The watchdog has been completed in v1.14. If a gpu crash because of high oc and don't report hashrate in 3 minutes, the watchdog will restart the thread.
This will improve the performance on rigs with "has timed out" messages.

Every time the EPOC changes, TBMiner have to recalculate the DAG buffer.
If the rig is tuned too high clocks, v1.00 - v1.13 could crash with "has timed out" messages.


[moderator's note: consecutive posts merged]
jr. member
Activity: 87
Merit: 5
When I start the miner I always got these warnings, is it normal?

│[2021-10-12 08:08:40][info][miner/0]:      0m [2021-10-12 08:08:38.199] Cannot initialize API server. Port in use. Retrying in 6 secs                                                                   
│[2021-10-12 08:08:40][info][miner/0]:      0m [2021-10-12 08:08:38.218] GPU5 Dag buffer verified ok!                                                                                                   
│[2021-10-12 08:08:42][info][miner/0]:      0m [2021-10-12 08:08:40.691] Job d99abc21                                                                                                                   
│[2021-10-12 08:08:43][info][miner/0]:      0m [2021-10-12 08:08:41.434] Job 7f2c7774                                                                                                                   
│[2021-10-12 08:08:46][info][miner/0]:      0m [2021-10-12 08:08:44.199] Cannot initialize API server. Port in use. Retrying in 6 secs                                                                   
│[2021-10-12 08:08:46][info][miner/0]:      0m [2021-10-12 08:08:44.408] Job 0be78c4e                                                                                                                   
│[2021-10-12 08:08:49][info][miner/0]:      0m [2021-10-12 08:08:47.380] Job c2223eb4                                                                                                                   
│[2021-10-12 08:08:51][info][miner/0]:      0m [2021-10-12 08:08:49.610] Job 5978c555                                                                                                                   
│[2021-10-12 08:08:52][info][miner/0]:      0m [2021-10-12 08:08:50.200] Cannot initialize API server. Port in use. Retrying in 6 secs                                                                   
│[2021-10-12 08:08:55][info][miner/0]:      0m [2021-10-12 08:08:53.327] Job 68aae417                                                                                                                   
│[2021-10-12 08:08:58][info][miner/0]:      0m [2021-10-12 08:08:56.200] Cannot initialize API server. Port in use. Retrying in 6 secs                                                                   
│[2021-10-12 08:08:58][info][miner/0]:      0m [2021-10-12 08:08:56.299] Job e3bdd953                                                                                                                   
│[2021-10-12 08:09:01][info][miner/0]:      0m [2021-10-12 08:08:59.272] Job 86b4891b                                                                                                                   
│[2021-10-12 08:09:04][info][miner/0]:      0m [2021-10-12 08:09:02.200] Cannot initialize API server. Port in use. Retrying in 6 secs                                                                   
│[2021-10-12 08:09:04][info][miner/0]:      0m [2021-10-12 08:09:02.245] Job 9f793b52                                                                                                                   
│[2021-10-12 08:09:07][info][miner/0]:      0m [2021-10-12 08:09:05.218] Job 111e356d                                                                                                                   
│[2021-10-12 08:09:10][info][miner/0]:      0m [2021-10-12 08:09:08.200] Cannot initialize API server. Port in use. Retrying in 6 secs                                                                   
│[2021-10-12 08:09:10][info][miner/0]:      0m [2021-10-12 08:09:08.933] Job 2aa7c9b6                                                                                                                   
│[2021-10-12 08:09:13][info][miner/0]:      0m [2021-10-12 08:09:11.906] Job 5da54083 
member
Activity: 118
Merit: 10
1-2 times 1.13 got lagging, so no new entry to see, gpu temp also show no mining because its cold. Faith enter helped.
So go back to 1.11 same if you mark something in the miner, or slide up with the bar and hold there. It seems after Enter it starts again, and gpu temp is raising.
Hope you understand my bad english Smiley
jr. member
Activity: 87
Merit: 5
Testing Flexpool with xintensity 896:

│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269] flexpool.io (ethash)    PING: 26ms    DIFFICULTY: 0.931    EPOCH: 446                                                           
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269]                                                                                                                                 
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269]                                                                                                                                 
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269] ID      BOARD   TYPE    TEMP    FAN     CORE    MEM     WATT    kW/h    COST/h   
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269] GPU0   3080    Cuda    50/0    55      1050    10201   224     0.22    0.02USD     
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269] GPU1   3080    Cuda    43/0    50      1050    10201   217     0.22    0.02USD     
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269] GPU2   3080    Cuda    51/0    50      1050    10201   222     0.22    0.02USD     
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269] GPU3   3080    Cuda    49/0    50      1050    10201   221     0.22    0.02USD                                                 
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.269] GPU4   3080    Cuda    50/0    54      1050    10201   215     0.21    0.02USD                                                 
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270] GPU5   3080    Cuda    50/0    56      1050    10201   221     0.22    0.02USD       
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270]                                                      1320    1.32    0.13USD       
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270]                                                                                     
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270] ID      BOARD   HASHRATE/W      HASHRATE        AVERAGE         SHARES               
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270] GPU0   3080    455.01 kH/W     101.92 MH/s     102.13 MH/s     36/0/8 (100.00%)     
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270] GPU1   3080    471.69 kH/W     102.36 MH/s     102.31 MH/s     29/0/5 (100.00%)       
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270] GPU2   3080    460.93 kH/W     102.33 MH/s     102.31 MH/s     21/0/3 (100.00%)     
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270] GPU3   3080    462.98 kH/W     102.32 MH/s     102.31 MH/s     21/0/3 (100.00%)       
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270] GPU4   3080    475.96 kH/W     102.33 MH/s     102.32 MH/s     23/0/2 (100.00%)       
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270] GPU5   3080    463.04 kH/W     102.33 MH/s     102.32 MH/s     25/0/3 (100.00%)       
│[2021-10-12 07:39:34][info][miner/0]:     19m [2021-10-12 07:39:33.270]              2789.60 kH/W    613.59 MH/s     613.70 MH/s     155/0/24 (100.00%)         
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
Only with core-lock 1.10 and newer will be as fast as 1.09. What i dont like in 1.09 - high cpu usage.

Core lock? Increase the Temp limit so the cards don't trottle.

The cpu usage in 1.09 is increasing the hashrate with 1-2% on low intensity but using too much power to be justified. We can add a flag --cpu-mining in the next version.

If you use 1.09 with --xintensity you have to multiply by 4 to compare the two versions.



Been running TBM 1.13 with xintensity 352 for 8 hours and my results are below:

485m [2021-10-11 20:07:37.418] ID           BOARD   HASHRATE/W   HASHRATE   AVERAGE      SHARES
485m [2021-10-11 20:07:37.418] GPU0   3060Ti   436.17 kH/W   64.99 MH/s   64.99 MH/s   133/0/0 485m
[2021-10-11 20:07:37.418]                       2470.18 kH/W   389.84 MH/s   389.85 MH/s   845/1/0 (99.88)

Looks good with no calculated stale shares. The most important is how is the payout / poolside reward?

Try with --xintensity 1408



Which xintensity should I set on Flexpool for the following cards to get the best performances?
  • NVIDIA RTX 3080 and 3070 (not LHR)
  • AMD RX 6800 and 6800 XT

On flexpool you should mine on the high difficulty port.

Why don't you try out 10 intensities and check yourself?

What hashrate are you getting with rtx 3080 --xintensity 1200 ?

Amd cards works best with lower --xintensities than NVIDIA

teamred miner: 58.8
s-eth.2miners.com:2020 (ethash)   DIFFICULTY: 2.03     EPOCH: 440
(At least 2 shares/10 mins at each intensity)
'Stock' settings - 6800xt (2400 clock / 1990 mem)
Xintensity =  -1: 62.32
Xintensity =   1: 58.51 - 213W
Xintensity =  12: 61.10
Xintensity =  24: 61.94
Xintensity =  36: 62.03
Xintensity =  48: 62.11
Xintensity =  78: 62.15
Xintensity = 128: 62.33
Xintensity = 240: 62.60
Xintensity = 360: 62.64
Xintensity = 512: 62.70 - 230W
No shares reject

[moderator's note: consecutive posts merged]
jr. member
Activity: 87
Merit: 5
Which xintensity should I set on Flexpool for the following cards to get the best performances?

  • NVIDIA RTX 3080 and 3070 (not LHR)
  • AMD RX 6800 and 6800 XT

Thanks.
jr. member
Activity: 212
Merit: 6
Still use 1.09 with better results than latest versions

Same here, if gpu is limited by tdp, any version after 1.09 will be much slower compared to any other miners. Only with core-lock 1.10 and newer will be as fast as 1.09. What i dont like in 1.09 - high cpu usage.
copper member
Activity: 77
Merit: 0
Is there a thread link to this suggestion?
Also, would that increase more stale shares submitted since we are increasing the xintensity?

Scroll a few pages back and look at the pictures.
Miningpoolhub pay 100% for stale shares so it doesn't matter. 2miners, nanopool, wollypooly 100% as well.
ezil.me 70% , hiveon.com 80%.

Flexpool, ethermine, nicehash, binance pay 0%. So the configuration of the mining software needs to be changed accordingly

Note that the ethereum blockchain rewards stale work/blocks. They are called uncle blocks. The uncle blocks are protecting the security of the blockchain.

For bitcoin based blockchains stale work is not rewarded and not needed.

Thanks for the explanation.

I updated the xintensity to 352 and currently mining on miningpoolhub.com.

Will provide results in the next 8-10 hours. Smiley

Been running TBM 1.13 with xintensity 352 for 8 hours and my results are below:

485m [2021-10-11 20:07:37.418] ID           BOARD   HASHRATE/W   HASHRATE   AVERAGE      SHARES
485m [2021-10-11 20:07:37.418] GPU0   3060Ti   436.17 kH/W   64.99 MH/s   64.99 MH/s   133/0/0 (100.00)
485m [2021-10-11 20:07:37.418] GPU1   3060Ti   362.99 kH/W   64.98 MH/s   64.98 MH/s   155/0/0 (100.00)
485m [2021-10-11 20:07:37.418] GPU2   3060Ti   435.92 kH/W   64.95 MH/s   64.95 MH/s   134/1/0 (99.26)
485m [2021-10-11 20:07:37.418] GPU3   3060Ti   363.04 kH/W   64.98 MH/s   64.98 MH/s   128/0/0 (100.00)
485m [2021-10-11 20:07:37.418] GPU4   3060Ti   435.91 kH/W   64.95 MH/s   64.96 MH/s   135/0/0 (100.00)
485m [2021-10-11 20:07:37.418] GPU5   3060Ti   436.15 kH/W   64.99 MH/s   64.99 MH/s   160/0/0 (100.00)
485m [2021-10-11 20:07:37.418]                       2470.18 kH/W   389.84 MH/s   389.85 MH/s   845/1/0 (99.88)
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
In the later versions on Nvidia you need to multiply the xintensity by 4 (cuda 11.4 build)

1.09: rtx 3080 --xintensity 300... ​109MHASH
1.13: rtx 3080 --xintensity 1200... 109MHASH

We nerfed it because of too many stale shares and poor results on some pools.
jr. member
Activity: 274
Merit: 1
Still use 1.09 with better results than latest versions
copper member
Activity: 77
Merit: 0
Is there a thread link to this suggestion?
Also, would that increase more stale shares submitted since we are increasing the xintensity?

Scroll a few pages back and look at the pictures.
Miningpoolhub pay 100% for stale shares so it doesn't matter. 2miners, nanopool, wollypooly 100% as well.
ezil.me 70% , hiveon.com 80%.

Flexpool, ethermine, nicehash, binance pay 0%. So the configuration of the mining software needs to be changed accordingly

Note that the ethereum blockchain rewards stale work/blocks. They are called uncle blocks. The uncle blocks are protecting the security of the blockchain.

For bitcoin based blockchains stale work is not rewarded and not needed.

Thanks for the explanation.

I updated the xintensity to 352 and currently mining on miningpoolhub.com.

Will provide results in the next 8-10 hours. Smiley
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
Is there a thread link to this suggestion?
Also, would that increase more stale shares submitted since we are increasing the xintensity?

Scroll a few pages back and look at the pictures.
Miningpoolhub pay 100% for stale shares so it doesn't matter. 2miners, nanopool, wollypooly 100% as well.
ezil.me 70% , hiveon.com 80%.

Flexpool, ethermine, nicehash, binance pay 0%. So the configuration of the mining software needs to be changed accordingly

Note that the ethereum blockchain rewards stale work/blocks. They are called uncle blocks. The uncle blocks are protecting the security of the blockchain.

For bitcoin based blockchains stale work is not rewarded and not needed.
copper member
Activity: 77
Merit: 0
On miningpoolhub try --xintensity 352 (suggested by one of the other users)

Is there a thread link to this suggestion?

Also, would that increase more stale shares submitted since we are increasing the xintensity?
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
On miningpoolhub try --xintensity 352 (suggested by one of the other users)



We are making a watchdog to be able to detect gpu's that are hanging / timed out. Hopefully done in v1.14




[moderator's note: consecutive posts merged]
copper member
Activity: 77
Merit: 0
https://github.com/sp-hash/TeamBlackMiner/releases/

1. Removed overflow in submit every x seconds.
2. Fixed Titan Xp boardname in the stats/api.
3. Added exception handling to fix crash on amd stats.
4. Reduced dag generation times on multicoin pools (zergpool,, nicehash etc))
5. API now return average hashrates instead of samples

TeamBlackMiner_1_13_cuda_11_2.7z
https://www.virustotal.com/gui/file-analysis/ZDJmYmVlOGI3MjgyYjQzMTM3ZjI3MTA3ZDZjNTU0MmI6MTYzMzg3MDY5MA==

TeamBlackMiner_1_13_cuda_11_4.7z
https://www.virustotal.com/gui/file/549d7a4b092cf611e56988450e4632a5adc01501b61b2de11e5d18aa80de3568?nocache=1

TeamBlackMiner_1_13_Ubuntu_18_04_Cuda_11_4
https://www.virustotal.com/gui/file/9dd6a4dac216df56cdd6584b9cae7d0da52802718ffd96c970e49cd57a312d6f?nocache=1




Is xintensity 224 still recommended for nvidia cards mining on miningpoolhub?
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
384m [2021-10-11 15:42:39.022] ID    BOARD   HASHRATE/W      HASHRATE        AVERAGE         SHARES
384m [2021-10-11 15:42:39.022] GPU0  5500XT  0.00 H/W        27.75 MH/s      27.85 MH/s      149/0/2 (100.00)

On the 5500XT try --xintensity 24, no stales poolside, lower power
Pages:
Jump to: