[ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 13.

micax1

hero member

Activity: 708

Merit: 502

Quote from: todxx on June 17, 2019, 12:11:53 AM

Quote from: micax1 on June 16, 2019, 11:56:54 PM

I have rig w rx 550s xmr stak works ok. however init of teamredminer fails like that:

[2019-06-17 07:55:22] Comm buf exit code timeout (fffffffe/8279/624952337/624952337/00000000).
[2019-06-17 07:55:22] Warning: failed to initialize device number 3 (-42), retrying.
[2019-06-17 07:55:27] Comm buf exit code timeout (fffffffe/8279/1551172833/1551172833/00000000).
[2019-06-17 07:55:27] Warning: failed to initialize device number 3 (-42), retrying.

Are you running a CPU miner at the same time by any chance?
Our init is a bit CPU intensive, and can timeout if there is another process running at 100% CPU usage.

that`s hive OS and no cpu mining.
I`ve also tried different init scenaries with same result

todxx

member

Activity: 176

Merit: 76

Quote from: micax1 on June 16, 2019, 11:56:54 PM

I have rig w rx 550s xmr stak works ok. however init of teamredminer fails like that:

[2019-06-17 07:55:22] Comm buf exit code timeout (fffffffe/8279/624952337/624952337/00000000).
[2019-06-17 07:55:22] Warning: failed to initialize device number 3 (-42), retrying.
[2019-06-17 07:55:27] Comm buf exit code timeout (fffffffe/8279/1551172833/1551172833/00000000).
[2019-06-17 07:55:27] Warning: failed to initialize device number 3 (-42), retrying.

Are you running a CPU miner at the same time by any chance?
Our init is a bit CPU intensive, and can timeout if there is another process running at 100% CPU usage.

micax1

hero member

Activity: 708

Merit: 502

I have rig w rx 550s xmr stak works ok. however init of teamredminer fails like that:

[2019-06-17 07:55:22] Comm buf exit code timeout (fffffffe/8279/624952337/624952337/00000000).
[2019-06-17 07:55:22] Warning: failed to initialize device number 3 (-42), retrying.
[2019-06-17 07:55:27] Comm buf exit code timeout (fffffffe/8279/1551172833/1551172833/00000000).
[2019-06-17 07:55:27] Warning: failed to initialize device number 3 (-42), retrying.

stepero

newbie

Activity: 45

Merit: 0

552 (sapphire, MSI)there is a gain to 550h/s, srb 440/s. Vega 56 (Hynix) 2000h/s. But at 584 (Samsung) the increase is minimal, staying at SRB.

dragonmike

hero member

Activity: 1274

Merit: 556

Quote from: kerney666 on June 08, 2019, 04:58:24 PM

Quote from: dragonmike on June 08, 2019, 04:11:36 PM

Arrrrh... Holy moly Batman, I lost my upx2 clocks and timings. That algo hits the hardware harder... Core clocks not as important as CN/r iirc, more like turtle, right?

Mikey, you’re in the wrong thread dammit Grin

.

That said, upx2 is much closer to turtle yes, even more of a bitch in terms of gpu load.

I know, wrong TRM thread, I noticed after I posted late last night... was hoping nobody would notice Tongue

Yeah annoying, UPX2. Tried some settings but they failed overnight. Gonna have to probably increase some voltages and loosen some timings before I run the autotuner again...

kerney666

member

Activity: 658

Merit: 86

Quote from: dragonmike on June 08, 2019, 04:11:36 PM

Arrrrh... Holy moly Batman, I lost my upx2 clocks and timings. That algo hits the hardware harder... Core clocks not as important as CN/r iirc, more like turtle, right?

Mikey, you’re in the wrong thread dammit Grin

.

That said, upx2 is much closer to turtle yes, even more of a bitch in terms of gpu load.

dragonmike

hero member

Activity: 1274

Merit: 556

Arrrrh... Holy moly Batman, I lost my upx2 clocks and timings. That algo hits the hardware harder... Core clocks not as important as CN/r iirc, more like turtle, right?

Transporter33

newbie

Activity: 3

Merit: 0

Quote from: todxx on June 08, 2019, 05:43:30 AM

Quote from: Transporter33 on June 08, 2019, 05:12:18 AM

Im getting "duplicate job detected' message. anyone know what causes this? its on X16r nanopool

Unfortunately this is caused by the pool sending the miner the same job multiple times. Some pools have taken the short-cut of sending out the same job twice when they want to change difficulty.
That said, unless you're getting reject shares, it shouldn't affect mining and you can just ignore the messages.

Thanks. shares seem ok. just having trouble with a hynix rx580 on CNR now, hashrate showing 950h but pool side only 650h.

petunder

newbie

Activity: 9

Merit: 0

Quote from: dragonmike on June 07, 2019, 05:39:43 AM

Quote from: petunder on June 07, 2019, 04:46:41 AM

X16R/Nicehash
Vega56 7 hrs average = 17 Mhs (1352gpu/900mem)
Vega 64 LQ 7 hrs average = 25 Mhs (1402/900)
average 7hrs power consumption on the wall 180W/GPU

Your Vega56 figure seems low... You should be closer to 21 (at least that's what I was getting when testing). Could there be anything slowing you down? Have you plugged a monitor to that GPU maybe?

Here 15 hrs stat. GPU0,2 - VEGA56 (flashed to 64), GPU1 - VEGA64 LQ

Code:

Stats Uptime: 0 days, 15:34:41
[2019-06-08 14:51:15] GPU 0 [60C, fan 0%] x16r: 16.52Mh/s, avg 17.50Mh/s, pool 17.07Mh/s a:2224 r:4 hw:0
[2019-06-08 14:51:15] GPU 1 [66C, fan 96%] x16r: 23.48Mh/s, avg 25.28Mh/s, pool 24.47Mh/s a:3197 r:4 hw:0
[2019-06-08 14:51:15] GPU 2 [61C, fan 0%] x16r: 16.56Mh/s, avg 17.66Mh/s, pool 17.02Mh/s a:2233 r:3 hw:0
[2019-06-08 14:51:15] Total x16r: 56.56Mh/s, avg 60.44Mh/s, pool 58.56Mh/s a:7654 r:11 hw:0

todxx

member

Activity: 176

Merit: 76

Quote from: Transporter33 on June 08, 2019, 05:12:18 AM

Im getting "duplicate job detected' message. anyone know what causes this? its on X16r nanopool

Unfortunately this is caused by the pool sending the miner the same job multiple times. Some pools have taken the short-cut of sending out the same job twice when they want to change difficulty.
That said, unless you're getting reject shares, it shouldn't affect mining and you can just ignore the messages.

Transporter33

newbie

Activity: 3

Merit: 0

Im getting "duplicate job detected' message. anyone know what causes this? its on X16r nanopool

todxx

member

Activity: 176

Merit: 76

Team Red Miner v0.5.1 released

https://github.com/todxx/teamredminer/releases

Changes in v0.5.1

Added better support for CN intensities 16*15, use --allow_large_alloc under Linux.
Added --no_ntime_roll for mining x16rt on e.g. bsod.pw.
Added Tonga device recognition.
Better error reporting for pool communication issues.

This release addresses a few minor issues people have reported in the v0.5.0 release.

hbouma

newbie

Activity: 22

Merit: 0

Quote from: NCarter84 on June 05, 2019, 06:21:19 PM

Roughly 73 mhs for a 6 card (four 580, two 590) on x16r, power under 870w.

Yeah, that's what I'm seeing although its a bit lower since I have 4 RX 470s and two RX 580s and the cards are undervolted. Unless I had totally screwed up my wildrig settings, this is a huge jump in performance.

Thanks TeamRedMiner!

Hal

dragonmike

hero member

Activity: 1274

Merit: 556

Quote from: petunder on June 07, 2019, 04:46:41 AM

X16R/Nicehash
Vega56 7 hrs average = 17 Mhs (1352gpu/900mem)
Vega 64 LQ 7 hrs average = 25 Mhs (1402/900)
average 7hrs power consumption on the wall 180W/GPU

Your Vega56 figure seems low... You should be closer to 21 (at least that's what I was getting when testing). Could there be anything slowing you down? Have you plugged a monitor to that GPU maybe?

petunder

newbie

Activity: 9

Merit: 0

X16R/Nicehash
Vega56 7 hrs average = 17 Mhs (1352gpu/900mem)
Vega 64 LQ 7 hrs average = 25 Mhs (1402/900)
average 7hrs power consumption on the wall 180W/GPU

GKumaran

member

Activity: 204

Merit: 10

Awesome Update :
Results for Vega 64, Aircooled, Reference
On Windows 10, 18.6.1 Driver, Timing mods

Algorithm	Hashrate	Power at wall (Watt)	Efficiency (Hash/Watt)	ODT Config	TRM Config
x16r, x16s, x16rt	(average- mh/s) 21.5	(average) 185	116.22	1082/ 800/812
CN R	2345	205	11.44	1408/1100/875	16*14:AAA
CN Saber	2185	177	12.35	1408/1100/875	15+15:CBB
CN Haven	2170	173	12.54	1408/1100/875	16+14:CBB
CN Turtle	22340	198	112.83	1216/1100/875	L26+26:AAA
CN UPX2	84940	208	408.37	1216/1100/875	L26+26:AAA or L26+26:BAA
CN HeavyX	1207	186	6.49	1408/1100/875	15*14:AAA

Note: The TRM config is just for info, use the auto tuning and get the best config for your card/clock/timings.

NCarter84

jr. member

Activity: 195

Merit: 4

Roughly 73 mhs for a 6 card (four 580, two 590) on x16r, power under 870w.

dragonmike

hero member

Activity: 1274

Merit: 556

Approx 21-22 MH/s on Vega56, 24-25 on Vega64. 12-14 on RX580. All, of course, at lower clocks and voltages than the competition. The rest is for you to test!

P00P135

full member

Activity: 1123

Merit: 136

Quote from: todxx on June 05, 2019, 03:10:30 PM

Team Red Miner v0.5.0 released

https://github.com/todxx/teamredminer/releases

Changes in v0.5.0

Added cryptonight 4MB variants: heavy, haven and saber.
Added x16 algo suite: x16r, x16s, x16rt (both gin and veil).
Auto-tuning mode for all CN variants, see bundled guide.
Manual key-driven CN tuning mode available inside the miner.
Additional data in miner stats console output.
Watchdog now detecting single stuck thread when mining CN.
Fix: in rare cases, poolside hash for compute algos (lyra2z, phi2, lyra2rev3) only reached ~95% of expected value.

We've added the x16* class of algos to TRM! Perhaps now Raven coin and friends won't be nvidia-only coins

Nice! Any GPU benchmarks for x16r? What can we expect to see?

todxx

member

Activity: 176

Merit: 76

Team Red Miner v0.5.0 released

https://github.com/todxx/teamredminer/releases

Changes in v0.5.0

Added cryptonight 4MB variants: heavy, haven and saber.
Added x16 algo suite: x16r, x16s, x16rt (both gin and veil).
Auto-tuning mode for all CN variants, see bundled guide.
Manual key-driven CN tuning mode available inside the miner.
Additional data in miner stats console output.
Watchdog now detecting single stuck thread when mining CN.
Fix: in rare cases, poolside hash for compute algos (lyra2z, phi2, lyra2rev3) only reached ~95% of expected value.

We've added the x16* class of algos to TRM! Perhaps now Raven coin and friends won't be nvidia-only coins

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