Quote from: kerney666 on April 18, 2019, 09:02:13 PM

Quote from: rednoW on April 18, 2019, 08:02:29 PM

Quote from: kerney666 on April 18, 2019, 06:38:07 PM

Quote from: rednoW on April 18, 2019, 06:06:15 PM

Quote from: plox99 on April 18, 2019, 05:33:03 PM

Quote from: rednoW on April 18, 2019, 05:25:47 PM

Quote from: kerney666 on April 18, 2019, 04:42:02 PM

Hi!

For everyone testing modded mem timings for CN using TeamRedMiner:

TRM v0.4.4 is released on GitHub (https://github.com/todxx/teamredminer/releases).

The release contains a new *-mode specifically targeted towards Vega GPUs with modded mem timings and running normal CN variants (not Turtle). Its the new default mode for Vegas.

The release also contains a new tuning guide with recipes for Vegas. Using it we can produce seriously sexy hashrates on all Vegas without increasing core clock above 1407 MHz (CN/r: 2440 h/s V64, 2250 h/s V56@64, 2130 h/s 56 Hynix).

The release will be in alpha state for a few hours before we post in our Bitcointalk topic, if anyone has the chance to take it for a spin, please do so and let us know your CN/r results.

Cheers, K

Nice, from 1.75 to 2.03 kh/s increase for cn/r from 0.4.3 to 0.4.4. vega56 hynix 1200/940@775mv (gpu-z shown clocks and voltage) Same timings

How about power? How many watts?

I don't know, 98watt gpu power in gpu-z. The same as trtl with 0.4.3
config 16*16 doesn't work for my vegas64 and 19.4.1 drivers. 14*14 config is ok and I'm getting 2.33kh/s (1300/1090@825mv 120 watt gpu-z )

Should have been more clear reg the *-mode: turtle is fine with the old + mode. The new mode is for all 2MB pad variants.

For power: weve seen increased efficiency across the board. A rule of thumb has been +2x% hashrate increase for +x% power, one example was a Vega 64 with +15% hashrate and +7.8% power draw.

I mean that cn-r (monero) doesn't work with 16*16 config in my case for vega64 - dead gpu in miner window. I had to decrease it to 14*14 and it is fine. Moreover my samsung vega56 with stock bios and custom timings (1230/950@775mv) is doing 2.1kh/s with 12*12 config vs. 2.06 with 14*14. Maybe it is how 19.4.1 drivers work ...
vega56 hynix is feeling better with 14*14 (2.03 kh/s)

Yeah, 16*16 will never work, it would use the full 8GB of vram for pads. Its a mess that the drivers allow the allocation. Use 15*15 instead. Have we written 16*16 somewhere, or even default to it?

The behavior of the 19.4.1 drivers is odd. Unless you run two massive monitors on that gpu, theres no reason for 12*12 to be better, rather the opposite.

Oh, my bad! I get used to increment of 2 for config in your miner ))
Now tested some ODD numbers.
And it helps! Best config for my vega56 is 13+13, samsung is doing 2.12kh/s, hynix 2.09kh/s
For vega64 15+15 is not the best. 14+14 is better (2.39kh/s with 1100mem clock).
Seems that 19.4.1 drivers don't like max mem load