⛏Team Black Miner (ETHB3 ETHW ETC VTC KAWPOW FIROPOW ZIL +dual +tripple mining )

[sp_]

So all things being equal, is a kernel 7 (TBM 1.16) on a RTX 3080 faster compared to whatever kernel was used in 1.15?

no. The cuda 11.2 build has been optimized.
In v1.16 cuda 11.4 #6 is faster. Or it depends on your launch config. There was a user who asked for 110MHASH. Why don't you try
If you run at 50% tdp, the program will select the fastest kernel for your config automaticly.

[1714698919]

1714698919

[1714698919]

1714698919

[1714698919]

1714698919

[1714698919]

1714698919

[1714698919]

1714698919

[BitBlitzer]

Yea I have already broken that!

I have a few cards with aluminium shims instead of thermal pads and can max the memory to +2000. Gives around 111.5MH/s (reported speed). Memory temps drop like crazy with aluminium/copper shims.

[sp_]

Gives around 111.5MH/s (reported speed).

That would be a new record hashrate. Why don't you upload a screenshot?

Poolside has also been improved on many pools with --xintensity 192 (default)

My mixed card rig 1070ti x 3, 3060 x 1 , 2060 x 1 running on v1.16 is doing the same speed with --xintensity 192  --xintensity 400 in v1.15. '

Less stale shares, more profit.

On AMD the last --xintensity change wasn't included in the build, so use manual tuning. Default -1 can be unstable.

[BitBlitzer]

https://imgur.com/a/VSUIBab

I just started it for the image but it's above 111MH/s on atleast one of the GPUs (MSI Ventus 3080). Still doing the serious mining on T-rex for now but might change for a new test soon.

[sp_]

I just started it for the image but it's above 111MH/s on atleast one of the GPUs (MSI Ventus 3080). Still doing the serious mining on T-rex for now but might change for a new test soon.

That is a really good hashrate.

[BitBlitzer]

Yea, thanks! Aluminium shims can take some cards to the next level but on some cards the memory just runs cooler but you cannot clock it higher.

[sp_]

Your card use less power and heat with locked core clock

to lock the clocks run the miner as admin and add this:

--lock-cclock [[1200,1200],[1200,1200],[1200,1200],[1200,1200],[1200,1200],[1200,1200]]

you need to find the correct lock clockrate at the right powerlimit

When testing you should also check in the logfile if one of the gpu's times out and restarts, or the miner is restarting. A timout can cause a 3 minute ++ loss of hashrate

[BitBlitzer]

When you lock the card in MSI Afterburner you override the powerlimit. The powerlimit doesn't effect the powerconsumption at all. It's basically the same thing as using --lock-clock in TBM or with nvidia-smi. All the cards are locked in MSI Afterburner and they are stable like this 24/7 with T-rex.

[sp_]

When you lock the card in MSI Afterburner you override the powerlimit. The powerlimit doesn't effect the powerconsumption at all. It's basically the same thing as using --lock-clock in TBM or with nvidia-smi. All the cards are locked in MSI Afterburner.

TBMiner v1.16 support setting the powerlimit too. If you set the lock clock too high, the core will trottle. Higher coreclock more heat, more cooling needed, so you want stable clocks, stable fanspeeds.

[BitBlitzer]

When you lock the card in MSI Afterburner you override the powerlimit. The powerlimit doesn't effect the powerconsumption at all. It's basically the same thing as using --lock-clock in TBM or with nvidia-smi. All the cards are locked in MSI Afterburner.

TBMiner v1.16 support setting the powerlimit to. If you set the lock clock too high, the core will trottle. Higher coreclock more heat, more cooling needed, so you want stable clocks, stable fanspeeds.

Ok, good to know!

But when you reach memory speeds of around +1500 or higher you need to push the core above 1200Mhz to reach maximum speed. I found you need atleast 1470Mhz for the GPU not to bottleneck the memory when the memory is at +2000.

[sp_]

But when you reach memory speeds of around +1500 or higher you need to push the core above 1200Mhz to reach maximum speed. I found you need atleast 1470Mhz for the GPU not to bottleneck the memory when the memory is at +2000.

you can try to play with the --kernel number. Low kernel number, stable on higher clocks

[LHiRtibkc6]

I'm happy to say the defaults in v1.16 are proving to be competitive on flexpool so far.

Especially for RTX 3080, RTX 3090, and RX 6800. The effective hashrate matches or exceeds the same setup with gminer now, even with the little bit more stales .

RTX 3070 and 3060Ti still seem to not accept the same level of memory overclocks. They have to be adjusted down -100 to -250 MHz to get past the DAG generation phase and the decrease shows in the effective hashrate.

[Ramsete2]

HELP! It seems that "--worker_name" command line is no more recognized in ver 1.16
I got this error on startup and miner won't start

Using same syntax of ver 1.15, nothing changed:

--algo ethash --hostname %pool_server% %pool_protocol% %pool_port% --wallet %user% --worker_name %rig_name% --api --api-ip 127.0.0.1 --api-port %api_port% --xintensity 192

[sp_]

HELP! It seems that --worker_name is no more recognized in ver 1.16
I got this error on startup and miner won't start

rename --worker_name
to --worker-name

[Ramsete2]

HELP! It seems that --worker_name is no more recognized in ver 1.16
I got this error on startup and miner won't start

rename --worker_name
to --worker-name

Thanks, better you’ll update your wiki:

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

[sp_]

RTX 3070 and 3060Ti still seem to not accept the same level of memory overclocks. They have to be adjusted down -100 to -250 MHz to get past the DAG generation phase and the decrease shows in the effective hashrate.

The easy fix is to run the lock-cclock, lock-mclock, power-limit after the dag buffer has been generated. But then you need to run the miner as admin, and let us clock the cards for you. The delayed clocking might be included in v1.17

[sp_]

I just started it for the image but it's above 111MH/s on atleast one of the GPUs (MSI Ventus 3080).

There is a big difference between 111MHASH and 100MHASH. Play with --kernel, --xintensity, --lock-cclock, --lock-mclock and power limit to tune the rig. Perhaps you can get all the cards to run faster than 108 MHASH with some more tweaking?.. I had a user on reddit who bought a new PSU and gained a few MHASH'es. More power, but +10% more money in the pocket might be worth it...



To all of those who ask for Hiveos integration both on pm, on reddit and in the thread, I just got a message from the HiveOS Community manager that they are working to add The Team Black miner this week.



v1.17
1. Fixed --xintensity -1 (dynamic) on AMD cards
2. Don't add hashrate to average hashrate when validating the dag file.
3. API bumped to v1.2. Added DAG generation to "threads" API call.
4. Core/mem clocks and powerlimit are set after DAG generation.
5. Added a few seconds of mining at startup. (while checking the dag buffer)
6. Reduce the stales on xintensity -1 (AMD)

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

https://www.virustotal.com/gui/file/60e0f121f9a99fccad3f0379b4a3d4c11128e858ce5ffd13b47df81a6df449a0?nocache=1
TeamBlackMiner_1_17_cuda_11_4.7z

https://www.virustotal.com/gui/file/56588e6c15d2dc21f455e6f8e45c5dd17037a3d9e3b2106755fb64ba7554280e?nocache=1
TeamBlackMiner_1_17_cuda_11_2.7z

TeamBlackMiner_1_17_Ubuntu_18_04_Cuda_11_4.zip
https://www.virustotal.com/gui/file-analysis/ZGFkODFkODhjMjNmMzg0OWQxNWQ5ZGViMDc3NmRjNmM6MTYzNDcxOTQ3NA==

RTX 3070 and 3060Ti still seem to not accept the same level of memory overclocks. They have to be adjusted down -100 to -250 MHz to get past the DAG

The delayed clocking might be included in v1.17

Delayed clock added in v1.17 as default

[moderator's note: consecutive posts merged]

[sabercrypto]

To all of those who ask for Hiveos integration both on pm, on reddit and in the thread, I just got a message from the HiveOS Community manager that they are working to add The Team Black miner this week.

at last

[Jeggu]

Any plans on optimizing the miner for LHR cards? I've got a couple 3080 tis looking for a home.

Yes. Which of teams has the fastest LHR kernel ?

T-rex is the fastest currently.

[matmator]

The reported hashrate on ethermine is working fine here. Why don't you share your realtime mining link so we can investigate.



gtx 1660 with memtweak (bios mod) ~35MHASH !

--kernel 0 / GPUMemoryTransferRateOffsetAllPerformanceLevels=1700

57m [2021-10-18 17:57:42.023] GPU0 1660S 0.00 H/W 34.98 MH/s 35.01 MH/s 18/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU1 1660S 0.00 H/W 35.14 MH/s 35.11 MH/s 29/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU2 1660S 0.00 H/W 35.18 MH/s 35.10 MH/s 22/0/1 (100.00%)
57m [2021-10-18 17:57:42.023] GPU3 1660S 0.00 H/W 35.10 MH/s 35.01 MH/s 22/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU4 1660S 0.00 H/W 33.33 MH/s 33.49 MH/s 24/0/1 (100.00%)
57m [2021-10-18 17:57:42.023] GPU5 1660S 0.00 H/W 33.43 MH/s 33.47 MH/s 21/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU6 1660S 0.00 H/W 35.02 MH/s 34.96 MH/s 26/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU7 1660S 0.00 H/W 34.83 MH/s 34.96 MH/s 32/0/1 (100.00%)
57m [2021-10-18 17:57:42.023] GPU8 1660S 0.00 H/W 35.03 MH/s 35.03 MH/s 20/0/1 (100.00%)
57m [2021-10-18 17:57:42.023] GPU9 1660S 0.00 H/W 35.03 MH/s 35.03 MH/s 24/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU10 1660S 0.00 H/W 35.09 MH/s 35.01 MH/s 32/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU11 1660S 0.00 H/W 34.94 MH/s 35.00 MH/s 29/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU12 1660S 0.00 H/W 32.47 MH/s 32.42 MH/s 25/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU13 1660S 0.00 H/W 35.16 MH/s 35.09 MH/s 30/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] 0.00 H/W 484.71 MH/s 484.68 MH/s 354/0/4 (100.00%)

--kernel 0 low power,cards with few shaders, low intensity
..
--kernel 7 higher power good on cards with many shaders, high intensity

If your rig has low tdp, low intensity, autotune will probobly select a lower number kernel.
The rtx 3060 and up works best on 5-7
The gtx 1070 has a new record speed on kernel #4

[moderator's note: consecutive posts merged]