[ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More

[PIOUPIOU99]

32+32 no stable
L for 64 with my rig win10 pro 18.6.1 is no good .
Test: 32+30 = good .

L28+26  for 56 hynix us very good  : 18.41 kh/s

I test better tonight.

Big thanks dev .

[logicus]

19.5 kh/s on ref Vega 56s flashed to V64 bios. Vega 56 it's L28+28.

Nice performance jump guys !!

[dragonmike]

Just tried this, running 6x reference Vega 56 (flashed to 64) at 1458/1107, using --cn_config=L24+24 I am sporting ~19.55 kh/s per GPU.

Rig draws around 1225W at the wall at these clocks.

I'd say pretty good work as usual, Kerney & Tod!

[fluxy12]

Running it on rx580 8gb, i got 8.6Kh@128W or 8Kh/s@109W downvolting.

[NCarter84]

Running it on rx580 8gb, i got 8.6Kh@128W or 8Kh/s@109W downvolting.

Been messing with one of mine... But RX570 4gb L16+16 and seem to be running 8.2 khs.

I haven't found any better combos than that for the config.

[rambetiko]

L28+28 on the 64 and L24+24 on the 56

which use pool for turtlecoin? this miner need stratum pool

[kerney666]

L28+28 on the 64 and L24+24 on the 56

which use pool for turtlecoin? this miner need stratum pool

There are a lot of pools: cryptoknight.cc, miner.rocks, cryptonote.social, etc. Right now I think pool ops are competing to be the first to get a fully functional LOKI+TRTL merged mining setup going, that would actually be kind of sweet for miner returns.

[dafuzz_rsa]

xfx vega 56 double edition(Hynix)
1368/900 900mv
L28+26

Not quite getting what others are.  Have tried various settings with cn_config
also seeing some hashrate drop after a few shares. cards all start out around 17.4kh

GPU 0 [59C, fan 29%] cnv8_trtl: 17.44kh/s, avg 17.43kh/s, pool 24.27kh/s a:16 r:0 hw:0  
GPU 1 [59C, fan 17%] cnv8_trtl: 16.41kh/s, avg 16.70kh/s, pool 2.580kh/s a:5 r:0 hw:0
GPU 2 [60C, fan 26%] cnv8_trtl: 17.79kh/s, avg 17.66kh/s, pool 23.35kh/s a:5 r:0 hw:0
GPU 3 [60C, fan 28%] cnv8_trtl: 17.44kh/s, avg 17.44kh/s, pool 806.4 h/s a:2 r:0 hw:0
GPU 4 [60C, fan 20%] cnv8_trtl: 16.46kh/s, avg 16.46kh/s, pool 17.91kh/s a:6 r:0 hw:0  
GPU 5 [59C, fan 32%] cnv8_trtl: 17.47kh/s, avg 17.47kh/s, pool 13.81kh/s a:5 r:0 hw:0
GPU 6 [59C, fan 27%] cnv8_trtl: 17.50kh/s, avg 17.50kh/s, pool 49.98kh/s a:10 r:0 hw:0
GPU 7 [59C, fan 24%] cnv8_trtl: 15.60kh/s, avg 16.56kh/s, pool 11.78kh/s a:6 r:0 hw:0  
GPU 8 [60C, fan 29%] cnv8_trtl: 17.50kh/s, avg 17.50kh/s, pool 8.857kh/s a:5 r:0 hw:0
GPU 9 [59C, fan 22%] cnv8_trtl: 17.48kh/s, avg 17.47kh/s, pool 2.260kh/s a:3 r:0 hw:0
 Total                cnv8_trtl: 171.1kh/s, avg 172.2kh/s, pool 155.6kh/s a:53 r:0 hw:0    

[kerney666]

xfx vega 56 double edition(Hynix)
1368/900 900mv
L28+26

Not quite getting what others are.  Have tried various settings with cn_config
also seeing some hashrate drop after a few shares. cards all start out around 17.4kh

GPU 0 [59C, fan 29%] cnv8_trtl: 17.44kh/s, avg 17.43kh/s, pool 24.27kh/s a:16 r:0 hw:0  
GPU 1 [59C, fan 17%] cnv8_trtl: 16.41kh/s, avg 16.70kh/s, pool 2.580kh/s a:5 r:0 hw:0
GPU 2 [60C, fan 26%] cnv8_trtl: 17.79kh/s, avg 17.66kh/s, pool 23.35kh/s a:5 r:0 hw:0
GPU 3 [60C, fan 28%] cnv8_trtl: 17.44kh/s, avg 17.44kh/s, pool 806.4 h/s a:2 r:0 hw:0
GPU 4 [60C, fan 20%] cnv8_trtl: 16.46kh/s, avg 16.46kh/s, pool 17.91kh/s a:6 r:0 hw:0  
GPU 5 [59C, fan 32%] cnv8_trtl: 17.47kh/s, avg 17.47kh/s, pool 13.81kh/s a:5 r:0 hw:0
GPU 6 [59C, fan 27%] cnv8_trtl: 17.50kh/s, avg 17.50kh/s, pool 49.98kh/s a:10 r:0 hw:0
GPU 7 [59C, fan 24%] cnv8_trtl: 15.60kh/s, avg 16.56kh/s, pool 11.78kh/s a:6 r:0 hw:0  
GPU 8 [60C, fan 29%] cnv8_trtl: 17.50kh/s, avg 17.50kh/s, pool 8.857kh/s a:5 r:0 hw:0
GPU 9 [59C, fan 22%] cnv8_trtl: 17.48kh/s, avg 17.47kh/s, pool 2.260kh/s a:3 r:0 hw:0
 Total                cnv8_trtl: 171.1kh/s, avg 172.2kh/s, pool 155.6kh/s a:53 r:0 hw:0    

Yeah there's def a variance here. Ref V56s flashed to V64 bios and true Vega 64s all seem to be straightforward to get hashing > 19 kh/s. I have a few things to test, but I need to get a few Vega 56s going that aren't flashed with the V64 bios.

Are you on win10 or linux? And, I assume you've tried configs like L24+24 and 28+28?

[rednoW]

welldone! ref vega 56 samsung with stock bios real gpu clock ~1330mhz, mem clock 940mhz, 850mv => 19,4 khs!
Pitty, that my vega64 liquids are doing only 0,2khs better with 1100 mem clock and 1370 gpu clock, 875mv

vega56 sapphire pulse with hynix - max I was able to get - 18.4khs

[rambetiko]

L28+28 on the 64 and L24+24 on the 56

which use pool for turtlecoin? this miner need stratum pool

There are a lot of pools: cryptoknight.cc, miner.rocks, cryptonote.social, etc. Right now I think pool ops are competing to be the first to get a fully functional LOKI+TRTL merged mining setup going, that would actually be kind of sweet for miner returns.

possible merged mining? where pool?
thanky you

[PIOUPIOU99]

For my 56 Sapphire hynix 1450/850
950/850  win10 .
No bios mod .
L24+24 or L28+26

[dafuzz_rsa]

snip

Yeah there's def a variance here. Ref V56s flashed to V64 bios and true Vega 64s all seem to be straightforward to get hashing > 19 kh/s. I have a few things to test, but I need to get a few Vega 56s going that aren't flashed with the V64 bios.

Are you on win10 or linux? And, I assume you've tried configs like L24+24 and 28+28?

Yea i tried them, best for me seems to be L28+26
on Linux

[kerney666]

welldone! ref vega 56 samsung with stock bios real gpu clock ~1330mhz, mem clock 940mhz, 850mv => 19,4 khs!
Pitty, that my vega64 liquids are doing only 0,2khs better with 1100 mem clock and 1370 gpu clock, 875mv

vega56 sapphire pulse with hynix - max I was able to get - 18.4khs

Nice, thanks for reporting back! This is interesting since it's a confirmed 19.4 kh/s for a ref V56 with _stock_ bios, although with samsung mem. The hynix nrs around 18.4 kh/s are also familiar, I've seen other users hitting the same nr.

And yeah, for this algo we can saturate the mem bandwidth with the samsung V56s. The diff between my ref V56s and my V64 LC is 19.50 vs 19.58 kh/s , pretty much the same experience as for you.

OS question though: I'm guessing this is on win10?

[kerney666]

snip

Yeah there's def a variance here. Ref V56s flashed to V64 bios and true Vega 64s all seem to be straightforward to get hashing > 19 kh/s. I have a few things to test, but I need to get a few Vega 56s going that aren't flashed with the V64 bios.

Are you on win10 or linux? And, I assume you've tried configs like L24+24 and 28+28?

Yea i tried them, best for me seems to be L28+26
on Linux

Hmm. I really need to get an amdgpu-pro environment going to be able to test better on linux as well. The memory subsystems on win vs linux are much more similar now than they were in e.g. the Blockchain driver days, but I wonder if the miner really behaves the same way on win vs linux for this algo at peak pressure.

[pbfarmer]

snip

Yeah there's def a variance here. Ref V56s flashed to V64 bios and true Vega 64s all seem to be straightforward to get hashing > 19 kh/s. I have a few things to test, but I need to get a few Vega 56s going that aren't flashed with the V64 bios.

Are you on win10 or linux? And, I assume you've tried configs like L24+24 and 28+28?

Yea i tried them, best for me seems to be L28+26
on Linux

Hmm. I really need to get an amdgpu-pro environment going to be able to test better on linux as well. The memory subsystems on win vs linux are much more similar now than they were in e.g. the Blockchain driver days, but I wonder if the miner really behaves the same way on win vs linux for this algo at peak pressure.

Hold my beer...

[kerney666]

snip

Yeah there's def a variance here. Ref V56s flashed to V64 bios and true Vega 64s all seem to be straightforward to get hashing > 19 kh/s. I have a few things to test, but I need to get a few Vega 56s going that aren't flashed with the V64 bios.

Are you on win10 or linux? And, I assume you've tried configs like L24+24 and 28+28?

Yea i tried them, best for me seems to be L28+26
on Linux

Hmm. I really need to get an amdgpu-pro environment going to be able to test better on linux as well. The memory subsystems on win vs linux are much more similar now than they were in e.g. the Blockchain driver days, but I wonder if the miner really behaves the same way on win vs linux for this algo at peak pressure.

Hold my beer...

Haha, yeah I was hoping you'd join the party! Very interesting to see if you can spot any clear differences between parameters such as OS/environments/drivers/gpu types/etc.

[pbfarmer]

snip

Yeah there's def a variance here. Ref V56s flashed to V64 bios and true Vega 64s all seem to be straightforward to get hashing > 19 kh/s. I have a few things to test, but I need to get a few Vega 56s going that aren't flashed with the V64 bios.

Are you on win10 or linux? And, I assume you've tried configs like L24+24 and 28+28?

Yea i tried them, best for me seems to be L28+26
on Linux

Hmm. I really need to get an amdgpu-pro environment going to be able to test better on linux as well. The memory subsystems on win vs linux are much more similar now than they were in e.g. the Blockchain driver days, but I wonder if the miner really behaves the same way on win vs linux for this algo at peak pressure.

Hold my beer...

Haha, yeah I was hoping you'd join the party! Very interesting to see if you can spot any clear differences between parameters such as OS/environments/drivers/gpu types/etc.

Haven't really done much in the past w/ CN light variants, as I got the impression they were a bit more power hungry... Is that the case w/ this (e.g. compared to cnv4)?  Just so I can get a sense of where to start my voltage settings.

[kerney666]

snip

Yeah there's def a variance here. Ref V56s flashed to V64 bios and true Vega 64s all seem to be straightforward to get hashing > 19 kh/s. I have a few things to test, but I need to get a few Vega 56s going that aren't flashed with the V64 bios.

Are you on win10 or linux? And, I assume you've tried configs like L24+24 and 28+28?

Yea i tried them, best for me seems to be L28+26
on Linux

Hmm. I really need to get an amdgpu-pro environment going to be able to test better on linux as well. The memory subsystems on win vs linux are much more similar now than they were in e.g. the Blockchain driver days, but I wonder if the miner really behaves the same way on win vs linux for this algo at peak pressure.

Hold my beer...

Haha, yeah I was hoping you'd join the party! Very interesting to see if you can spot any clear differences between parameters such as OS/environments/drivers/gpu types/etc.

Haven't really done much in the past w/ CN light variants, as I got the impression they were a bit more power hungry... Is that the case w/ this (e.g. compared to cnv4)?  Just so I can get a sense of where to start my voltage settings.

Not trivial to measure, there are a few different trade-offs in play, but I'd actually say they're about on par. CN-turtle uses the CNv8 main loop which (in our case) draws less power than the CN/r main loop, but CN-turtle does for sure put more load in general on the gpu than the 2MB pad variants.

[rednoW]

welldone! ref vega 56 samsung with stock bios real gpu clock ~1330mhz, mem clock 940mhz, 850mv => 19,4 khs!
Pitty, that my vega64 liquids are doing only 0,2khs better with 1100 mem clock and 1370 gpu clock, 875mv

vega56 sapphire pulse with hynix - max I was able to get - 18.4khs

Nice, thanks for reporting back! This is interesting since it's a confirmed 19.4 kh/s for a ref V56 with _stock_ bios, although with samsung mem. The hynix nrs around 18.4 kh/s are also familiar, I've seen other users hitting the same nr.

And yeah, for this algo we can saturate the mem bandwidth with the samsung V56s. The diff between my ref V56s and my V64 LC is 19.50 vs 19.58 kh/s , pretty much the same experience as for you.

OS question though: I'm guessing this is on win10?

yes, win10 with 19.3.3 drivers and level 1 timings