Pages:
Author

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

jr. member
Activity: 139
Merit: 3
use msi afterburner. We don't support sdtting the clocks on Amd cards

Better yet, use OverdriveNTool for AMD cards, much easier to set the OC script to run from the TBMiner script and to check that the values are holding.
jr. member
Activity: 90
Merit: 1
use msi afterburner. We don't support sdtting the clocks on Amd cards

Ah ok ok!

Thanks!
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
use msi afterburner. We don't support sdtting the clocks on Amd cards
jr. member
Activity: 90
Merit: 1
see the example launch config

tbminer_flexpool_eth.bat


I got the basics, I am running it on NVIDIAs,...
But for AMD 580 , I was asking mainly for OCs switches , this:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

and

-gt 68 -cclock 1130 -mclock 2200 -cvddc 850 -mvddc 850
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
see the example launch config

tbminer_flexpool_eth.bat
jr. member
Activity: 90
Merit: 1
Mr.sp__ , when can we expect update with DAG generate/verification on HDD?
Thanks!

I would also like to try your miner on my 580;
Considering I have this in .bat for 580s ( I have 3 of them in this rig )  , how should I need to run your config?

Code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

PhoenixMiner.exe -pool ssl://eth-us-east.flexpool.io:5555 -wal ADRESS -worker NAME -gt 68 -cclock 1130 -mclock 2200 -cvddc 850 -mvddc 850 -coin eth

pause

Help is appreciated!

Thanks
jr. member
Activity: 90
Merit: 1
Mr.sp__ , when can we expect update with DAG generate/verification on HDD?
Thanks!
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
Just confirming that Nvidia cards still have a 4x multiplier on the xintensity vs AMD cards right?

yes
jr. member
Activity: 139
Merit: 3
The only way to reduce stales on AMD is to change the pool or lower the xintensity. Did you try 24 or 48?
Having a low ping to the pool isn'tas important if the pool pay for stale shares. Read a few posts back and see the settings that can give you +10% poolside hashrates with TBM.

I am going to play around with some stuff, seems like the weaker cards (6600) hash better on the higher xint, and the more powerful (6800+) hash the same on lower xint while making less stales. Going to try various xint settings and report back. Just want to stay on flex since they have the lowest fee. Seeing you also have the lowest fee seems like a real match made in heaven.

The difference can be big. The high xintensity not only increases the stale shares, it increase the share coun and poolside profit.

6800xt

flexpool: 61MHASH (poolside) (low xintensity, and not paying for stales)
2miners: 67MHASH(poolside)

Just confirming that Nvidia cards still have a 4x multiplier on the xintensity vs AMD cards right?
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
The only way to reduce stales on AMD is to change the pool or lower the xintensity. Did you try 24 or 48?
Having a low ping to the pool isn'tas important if the pool pay for stale shares. Read a few posts back and see the settings that can give you +10% poolside hashrates with TBM.

I am going to play around with some stuff, seems like the weaker cards (6600) hash better on the higher xint, and the more powerful (6800+) hash the same on lower xint while making less stales. Going to try various xint settings and report back. Just want to stay on flex since they have the lowest fee. Seeing you also have the lowest fee seems like a real match made in heaven.

The difference can be big. The high xintensity not only increases the stale shares, it increase the share coun and poolside profit.

6800xt

flexpool: 61MHASH (poolside) (low xintensity, and not paying for stales)
2miners: 67MHASH(poolside)
newbie
Activity: 3
Merit: 0
The settings of --xintensity 512 and --tweak 6 would be for nvidia right?

Yes,. Tweak is not implemented for AMD yet.


I want to continue to use flexpool. It gives the best ping in my area. The rigs I am referring to are AMD RX6000 mixed rigs ONLY. I do not use TBM on Nvidia. I like your kernel better for AMD, than your competition, but I need further miner optimization to reduce stales on flex. As I mentioned I went from less than 0.5% stales on TRM to about 2% stales on TBM. Now my valids are still more than they were with TRM, but I would still like to reduce my stales. Should I run higher xint on weaker cards like 6600 and lower xint on more powerful cards like 6800xt? Any info appreciated TIA.

The only way to reduce stales on AMD is to change the pool or lower the xintensity. Did you try 24 or 48?
Having a low ping to the pool isn'tas important if the pool pay for stale shares. Read a few posts back and see the settings that can give you +10% poolside hashrates with TBM.

I am going to play around with some stuff, seems like the weaker cards (6600) hash better on the higher xint, and the more powerful (6800+) hash the same on lower xint while making less stales. Going to try various xint settings and report back. Just want to stay on flex since they have the lowest fee. Seeing you also have the lowest fee seems like a real match made in heaven.
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
The settings of --xintensity 512 and --tweak 6 would be for nvidia right?

Yes,. Tweak is not implemented for AMD yet. With tweak inplace it might help to reduce stales.


I want to continue to use flexpool. It gives the best ping in my area. The rigs I am referring to are AMD RX6000 mixed rigs ONLY. I do not use TBM on Nvidia. I like your kernel better for AMD, than your competition, but I need further miner optimization to reduce stales on flex. As I mentioned I went from less than 0.5% stales on TRM to about 2% stales on TBM. Now my valids are still more than they were with TRM, but I would still like to reduce my stales. Should I run higher xint on weaker cards like 6600 and lower xint on more powerful cards like 6800xt? Any info appreciated TIA.

The only way to reduce stales on AMD is to change the pool or lower the xintensity. Did you try 24 or 48?
Having a low ping to the pool isn'tas important if the pool pay for stale shares. Read a few posts back and see the settings that can give you +10% poolside hashrates with TBM.


newbie
Activity: 3
Merit: 0
Just switched all my RX6000 rigs over to TBM, saw HUGE improvement on submitted shares instantly, but went from like 0.3% stales using TRM to over 2% on TBM. I am on flexpool, miner sets that xintensity to 71 for flex. Anyone find a good number for xint on flex to reduce stales? Also seem to get invalid or rejects in the miner print I assume it goes accepted/rejected/invalid? But none reported by the pool. For example: 52/0/3. This only occurs on my Hive rigs, windows rigs seem to be all accepted. Glad to be with the black team now. Any info or help is appreciated!

Default intensity is 284 for NVIDIA and 71 for amd. You can try with --xintensity 512 and --tweak 6. Or change the pool and use --xintensity 4096 and get payed for the 5% stales.

https://github.com/sp-hash/TeamBlackMiner/blob/main/FAQ.md




The settings of --xintensity 512 and --tweak 6 would be for nvidia right? I want to continue to use flexpool. It gives the best ping in my area. The rigs I am referring to are AMD RX6000 mixed rigs ONLY. I do not use TBM on Nvidia. I like your kernel better for AMD, than your competition, but I need further miner optimization to reduce stales on flex. As I mentioned I went from less than 0.5% stales on TRM to about 2% stales on TBM. Now my valids are still more than they were with TRM, but I would still like to reduce my stales. Should I run higher xint on weaker cards like 6600 and lower xint on more powerful cards like 6800xt? Any info appreciated TIA.
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
Im stuck with HiveOn pool. So i don't want the stales. Im trying to find the best Xint to avoid them. And maybe make a test of 24hours of both miners.

Expect 5-10% less return on the hiveon pool. There is a bug that give rejected shares on this pool.Something is wrong with the Ethproxy stratum implementation.
jr. member
Activity: 60
Merit: 2
It was with 1.44. now with 1.45 i get decent hashrates. But Xintensity of 1024 is way to high. Almost 50% stales. Now with 128 i got no stales anymore in 30 minutes of mining. The hashrate is for 12 cards 10mhs slower then TRM.

mine with --xintensity 1024 on 2miners.com / nanopool.org/ miningpoolhub/ f2pool.com or other pools that pay for stales.. And get no stale penalty. The estimated stales reported in the miner window is wrong. TBM has 0.5% fee. TRM has 1% fee. A few MHASH faster might not cover the expensive fee.

https://github.com/sp-hash/TeamBlackMiner/blob/main/FAQ.md

Im stuck with HiveOn pool. So i don't want the stales. Im trying to find the best Xint to avoid them. And maybe make a test of 24hours of both miners.
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
It was with 1.44. now with 1.45 i get decent hashrates. But Xintensity of 1024 is way to high. Almost 50% stales. Now with 128 i got no stales anymore in 30 minutes of mining. The hashrate is for 12 cards 10mhs slower then TRM.

mine with --xintensity 1024 on 2miners.com / nanopool.org/ miningpoolhub/ f2pool.com or other pools that pay for stales.. And get no stale penalty. The estimated stales reported in the miner window is wrong. TBM has 0.5% fee. TRM has 1% fee. A few MHASH faster might not cover the expensive fee.

https://github.com/sp-hash/TeamBlackMiner/blob/main/FAQ.md
jr. member
Activity: 60
Merit: 2
This is what i get with TBM with the BC-160 cards. The Xintensity doesn't make any difference.

Is this the latest 1.45 version?

It was with 1.44. now with 1.45 i get decent hashrates. But Xintensity of 1024 is way to high. Almost 50% stales. Now with 128 i got no stales anymore in 30 minutes of mining. The hashrate is for 12 cards 10mhs slower then TRM.
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
This is what i get with TBM with the BC-160 cards. The Xintensity doesn't make any difference.

Is this the latest 1.45 version?
jr. member
Activity: 60
Merit: 2
This is what i get with TBM with the BC-160 cards. The Xintensity doesn't make any difference.

sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
The developer needs to conduct detailed tests for more than a day to stabilize his work while I return to LoL
To be fair, at the end of my 780 minute (13 hour) run, the median/mean hashrate for my 3090 was 181/182 MH/s with a STD.Dev of +/- 10 MH/s, so I'm not complaining.

We have alot of releases, but we also have 38 test cards that run the latest version 24/7 (AMD/NVIDIA). But we can't test all the different mining pools, and sometimes pools change their code. So if you find something, please report to our github, here or on reddit.

sp_ : are you planning on adding support for the BC-160 cards? I have 12 of them and i can't make it work with TBM (weird unstable speeds) for now the only miner i get decent speeds is TRM.

try with --xintensity 1024

Also seem to get invalid or rejects in the miner print I assume it goes accepted/rejected/invalid? But none reported by the pool. For example: 52/0/3.

The stale share estimate is way off because it also report level 1 stale shares. You should always check the pool for the stale count. Will fix it.

(accepted/rejected/estimated stale)


Just switched all my RX6000 rigs over to TBM, saw HUGE improvement on submitted shares instantly, but went from like 0.3% stales using TRM to over 2% on TBM. I am on flexpool, miner sets that xintensity to 71 for flex. Anyone find a good number for xint on flex to reduce stales? Also seem to get invalid or rejects in the miner print I assume it goes accepted/rejected/invalid? But none reported by the pool. For example: 52/0/3. This only occurs on my Hive rigs, windows rigs seem to be all accepted. Glad to be with the black team now. Any info or help is appreciated!

Default intensity is 284 for NVIDIA and 71 for amd. You can try with --xintensity 512 and --tweak 6. Or change the pool and use --xintensity 4096 and get payed for the 5% stales.

https://github.com/sp-hash/TeamBlackMiner/blob/main/FAQ.md


I ran the test for more than a day and my hash dropped from 1345 to 1275 in the miner in about 27-28 hours. The pool averaged 1.26 gh/s over 6 hours

Check the log for error messages. Perhaps you had an epoc change? The temperature high on the memory? The miner should work stable for days. But you can try the mining time option

f.ex

--miningtime 1440

will restart the miner every 24 hours.

-k --miningtime             Only mine for x minutes.
                            Typically used to test different setups.
Pages:
Jump to: