⛏Team Black Miner (ETHB3 ETHW ETC VTC KAWPOW FIROPOW EVRPROGPOW MEOWPOW +dual)

[ayiphelmy]

10 mhs slower with 6 gpu rig, just try it a couple minute ago

What cards in the rig, which pool, which launch configuration?

1070ti, 2080ti, 2070 super, all default setup on miner command, ethermine pool

[sp_]

try v1.14..

I get 0.0055 eth from flexpool. A better poolside hashrate doesn't always mean a better revenue.

TBMiner  v1.14 on miningpoolhub default setting seem give around 5-10% more ethereum than flexpool on the default setting. poolside test. Higher poolside hashrate, higher payouts..

I'm still unsure which pool to use with 1-2% stales and 700 MH/s. Pools don't seem to publish how they treat stales.

Mining Pools change their code too.. Most of the mining pool sourcecode is based on bitcoin based blockchains and cpu mining. A cpu has 1-16 cores, and a search can be aborted quickly.

The rtx 3090 has 10496 cuda cores.(processors). When a pool ask the miner to do a seach, all the 10500 cores are used. TBMiner is letting the 10500 cores complete their task before starting on a new job. Some pools send out a job, and then another job just a few ms after. and then declining the work of the first job. This pool fuck is forcing the modern gpu to run at "cpu style" speeds. loosing 10-20% because it has to abort the work all the time.
The ethereum blockchain is rewarding stale work, proper written pool software can reward the extra 10-20% to the miners instead.

We have a sideproject to write a new poolsoftware in The Team Black. We will scrap the stratum protocol. Opensource code...


[moderator's note: consecutive posts merged]

[dle378]

For this release, do we still need to specify the xintensity value since by default it is configured to 1200?

No need if you mine on miningpoolhub, 2miners, nanopool and many others.

But

Flexpool, ethermine,  nicehash probobly need a lower --xintensity

I am running TBM 1.14 now and excluded the xintensity value in the parameters. However, I am seeing that the miner is auto selecting "224" instead of "1200".

Am I missing something here?

[sp_]

Try to download again

[dle378]

Try to download again

The newly uploaded TBM v1.14 resolved the issue as now I am seeing the default xintensity value of 1200.

Thanks!

[somaton]

All my gpus in all rigs are in P0 state for many years, it is something else.

Here in p0 clocks are stable except when temp is to hot, or the card doesn't have enough power.

Anyway v1.14 has been released. check it out. v1.14 has few detected stales on miningpoolhub on --xintensity 1200 (default) and the poolside profit is amazing.

If there is not enough power, then gpu will not clock to 1800 mhz. It is not temperature and not power. As i said, with 1.09 it is working perfectly, but newer versions only with core-lock.

I cant try 1.14 because of 470.05.

[dle378]

Nvidia just released their latest driver (496.13) and they updated the CUDA version to 11.5

Will there be an updated TBM version that supports CUDA version 11.5?

[sp_]

only with locked  core-lock.

What is the nvidia-smi syntax you use to lock the clock?

[KillrBee]

I jumped to a new milestone highest hash rate!  Although I think it might be a glitch since the hash rate afterwards was a more normal average (135ish), but for the sake of documenting it:

https://imgur.com/gallery/QgqjPFy

[sp_]

I jumped to a new milestone highest hash rate!  Although I think it might be a glitch since the hash rate afterwards was a more normal average (135ish), but for the sake of documenting it:

nice. Was this the 1.14 build on default settings?

[KillrBee]

I jumped to a new milestone highest hash rate!  Although I think it might be a glitch since the hash rate afterwards was a more normal average (135ish), but for the sake of documenting it:

nice. Was this the 1.14 build on default settings?

Yes, default intensity on the miner, clocks as shown, power level at 97%

[sp_]

I jumped to a new milestone highest hash rate!  Although I think it might be a glitch since the hash rate afterwards was a more normal average (135ish), but for the sake of documenting it:

with lock clock and the proper tuning, I beleve stable 140 is possible...We need to find the sweetspot between clocks and intensity. 1800 core clock instead of 1500 can drop a few mhashes. So faster clocks is not always better.. Nvidia cards clocks trottle at default, and it is hurting the performance... With the older cards you could set them to P0 state and the clockrate would be stable. The newest cards still trottle in p0 state...

[ZerodayTrader]

Hey guys,

any tipps to improve this 3080?

https://i.imgur.com/0tfYy1A.png
https://i.imgur.com/hR4UT4G.png

Or is there not much air left?

[sp_]

Hey guys,
any tipps to improve this 3080?


Or is there not much air left?

Thanks for posting

So there is a way to limit the clocks. Nice speed..

[ZerodayTrader]

So there is a way to limit the clocks.

Could u a bit more specific about that?

[sp_]

The voltage frequency editor is not available for linux

[ZerodayTrader]

Ahh!

And btw. noticed got some stale shares on my 1070 recently, any suggestions? Running with; --xintensity 224 --no-cpu

https://imgur.com/M8fXuoX.png
https://i.imgur.com/tZxxIJ7.png

[sp_]

Ahh!

And btw. noticed got some stale shares on my 1070 recently, any suggestions? Running with; --xintensity 224 --no-cpu

Rejected shares. Could be a pool problem?  check the logfile what's the pool error message? 4600 is high, reduce to 4400 and increase the core clock to 1950

Could u a bit more specific about that?

The voltage frequency editor is not available for linux

So moving from linux to windows and Team Black can get you a 10% free boost. Post it on reddit.

lock clocks has been added to the todo list...

[moderator's note: consecutive posts merged]

[ZerodayTrader]

Dont have a logfile.

[sp_]

add

--log                    (Enable logging)