Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 17. (Read 85791 times)

@todxx

You guys planning on supporting cryptonight_conceal at some point?

Cheers

Hi redzep,

It seems that the GPUs are crashing, probably due to the OC/UV profile you are running.
Even though your current settings might be stable on other miners/algos, different miners and algos will behave differently and have different OC/UV limits.
In this case, phi2 is a rather core heavy algo, and will probably require dropping your clocks a bit.
A good sanity check is to see if it works at stock clocks/voltages, and then go from there.

Hi got an issue mining phil2 Gway Coin, it did work few months back ok for AGM, cards work ok with X22i & X16r with no reboot after trying teamredminer
nothing has been updated in months on Rig and works fine with other miners

command line below
teamredminer.exe -a phi2 -o stratum+tcp://uk.thepool.life:5124 -u Wallet address -p c=GWAY -d 3,4

miner working fine on my PC to same pool

  Team Red Miner version 0.3.10
[2019-03-13 12:55:19] Auto-detected AMD OpenCL platform 0
[2019-03-13 12:55:22] Initializing GPU 0.
[2019-03-13 12:55:22] Watchdog thread starting.
[2019-03-13 12:55:22] Pool uk.thepool.life connecting to address 95.179.206.161.
[2019-03-13 12:55:22] Pool uk.thepool.life successfully connected to address 95.179.206.161.
[2019-03-13 12:55:22] Pool uk.thepool.life successfully subscribed. (8 ms)
[2019-03-13 12:55:23] Pool uk.thepool.life authorization succeeded.
[2019-03-13 12:55:23] Dev pool connected and ready.
[2019-03-13 12:55:23] Pool uk.thepool.life set difficulty to 1.000000
[2019-03-13 12:55:23] Pool uk.thepool.life received new job. (job_id: 1b0e)
[2019-03-13 12:55:23] Pool uk.thepool.life extranonce subscribe succeeded. (944 ms)
[2019-03-13 12:55:52] Stats Uptime: 0 days, 00:00:31
[2019-03-13 12:55:52] GPU 0 [45C, fan 59%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:55:52] GPU 1 [48C, fan 25%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:55:52] Total                phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:56:06] Pool uk.thepool.life received new job. (job_id: 1b0f)
[2019-03-13 12:56:22] Stats Uptime: 0 days, 00:01:01
[2019-03-13 12:57:02] GPU 0: detected DEAD (05:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:37] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:57:12] Pool uk.thepool.life received new job. (job_id: 1b10)
[2019-03-13 12:58:37] GPU 1: detected DEAD (08:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:37] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:58:37] Pool uk.thepool.life received new job. (job_id: 1b11)
[2019-03-13 12:58:37] GPU 0 [38C, fan 25%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:37] GPU 1 [48C, fan  0%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:37] Total                phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:47] GPU 0: detected DEAD (05:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:47] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:58:47] GPU 1: detected DEAD (08:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:47] Please use command line argument --watchdog_script to handle dead GPUs.


Thanks

fixed it saw earlier post about CPU mining which i stopped and working fine now

Well, i thought it was bigger. 1% for 1% shouldnt be something to bother with, if you ask me. It was mistake on my side with bad measurements.

Aight, so +0.47% perf increase for +1% power, hmm. Well, no disaster really, I haven't had to time to dig into it myself though. Like I sad, we've added a few small things host-side, and some smaller things gpu-side as well. Will try to run those checks myself shortly.

Yep you're spot on: total hashrate is displayed in miner, poolside (as displayed in miner and by the pool itself) should over time average out to miner - dev fee - reject ratio.

A general recommendation: for CN, I recommend everyone having doubts to run e.g. xmrig-proxy between a single rig and your pool with a configured local diff in xmrig-proxy of 1000 or so (a little depending on your rig's hashrate, can't go completely nuts). Run that setup until you have 50k accepted shares and check the number poolside in the miner, and of course in xmrig-proxy if you don't trust the miner itself. If you want a really tight estimate of your true poolside hashrate, you really need that high nr of shares found. For a little more realistic scenario, you could use a local diff of 10000, but then you'd have to wait 10x longer as well.

Okay tested again.

There is difference for sure, but not as big as i initially reported. 447W on 3.10, vs 451-452W on 4.1. Guess the initial big difference was because of the slightly different ambient temperatures...

just to clarify... dev fee... your % is including in the hashrate shown within the miner for CNR.

CN-R - 2.5% dev fee

Miner reports 1000hs....

Hashrate at pool should be around 975 hs.

Nevermind.

EDIT:  I am mixing up MTP with cuckoo here.

Reverse Waltz will be out in 2 days, is my guess right now.

Oh they got it working now? Finally, then people might asking for it . I don't see any mentions of it in the mining channel on their discord though. Last I checked they had it working for Polaris but not for Vegas, the Vega perf was much too low.

I'm very happy with the "unoptimized" Radeon VII performance. I'm getting 2700 H/s using 14+14 the card is also running my OS and youtube videos, etc. stably. I can't wait to see what the optimized performance will be. Also super happy ssl is working in this release. Thanks to the devs

CN8-RWZ = ??

I think we already have miners that do 3.5 MH on MTP and on Vega.

Hey, thanks for the kind words, much appreciated! We'll see what we do after this CN push. We will add a few CN variants, then move on to something else. I'm so surprised there isn't a good Vega MTP miner out by now. We know how to get them to 3-3.5 MH/s on MTP, but the power draw will be higher than Nvidia (that goes for any plain AMD MTP implementation though). C29/C31 might also be something to look at.

Hello i would like to give my thanks to whole team red for their hard work , your miner is without a doubt fastest  my uderclocked / biosmoded vegas hash better than when i bought them a year a back   each vega 2kh cryptonightr 175w at wall , lyra2rev3 84-88mh  , my WC vega 2600h cryptonightr, 112 mh lyra2rev3 im really happy to see those same hashrates reported by pools also
I would like to ask for  MTp / cuckoo cycle   algo support since there isnt any properly optimazed amd  miners out there for those new algos which are currently  most profitable , keep up good work

I will check again and test as well, to see if its not some weird behavior.

As for the exact number figures - yea, my bad, i did not read that post properly.

Hi! The changelog says +0.5%, which you’re spot on. Not sure where you saw 2-3%? This thread should also have been updated though, our bad.

For the power draw, that is strange. I can leak that the only thing that has changed is the last kernel, so small changes really. We do have some other changes host side, but it feels very odd that they would add 15-20W!?!

Will do some testing of my own shortly!

I am observing something weird.

With v0.3.10, i was  getting on Vertcoin (Lyra2rev3), 190.8Mh/s for ~435-440W at wall.
With v0.4.0, i am getting 191.7Mh/s for 450-455W at wall.

The claimed performance increase is 2-3%, but for me, in reality, is ~1%, while getting 2-4% power consumption increase.
Windows 10, AMD 19.2.1, using Memory P0 state.

1x RX 570, 3x RX 580.

Yes, I know that it's one miner. But different threads )))