|
81
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.8.6 - native algo switching
|
on: April 28, 2019, 09:55:49 PM
|
What is the default value for RFC on the samsung V56 ?
vega56 reference with samsung, stock timings according to Eliovp utility <values cl="17" ras="27" rcdrd="13" rcdwr="8" rcab="39" rcpb="39" rpab="12" rppb="12" rrds="3" rrdl="4" rtp="5" faw="13" cwl="6" wtrs="3" wtrl="7" wr="13" rrefd="7" rdrddd="3" rdrdsd="2" rdrdsc="1" rdrdscl="3" wrwrdd="3" wrwrsd="2" wrwrsc="1" wrwrscl="3" wrrd="1" rdwr="17" ref="3120" mrd="8" mod="12" xs="216" xsmrs="6" pd="6" cksre="8" cksrx="8" rfcpb="128" stag="7" xp="6" cpded="2" cke="6" rddata="16" wrlat="4" rdlat="14" wrdata="1" ckestag="2" rfc="208" timing="1" zerorpm="False" tdplimit="0" maxtemp="85"> |
|
|
|
|
83
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.8.6 - native algo switching
|
on: April 28, 2019, 11:20:15 AM
|
Hi, Dok!
Just examined your timings for profile 10.
They are good for hynix HBM2 but for samsung (both low voltage 800-940 mhz vega56 and high voltage 945-1100 mhz vega64 I have much better (more stable and fast) mem timings)
I can share to you if you want ))
You can share to help the folks here, im not using predefined straps in SRB. They are calculated based on existing settings. Ok, this is for Vega 64 LC  This if for reference vega56, stock bios  win10, 19.4.1 driver |
|
|
|
|
87
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.8.4 - native algo switching
|
on: April 20, 2019, 07:27:49 AM
|
2 doctor83
I don't think it is good idea to mix miner and memory timings optimizer in such manner. User should understand what benefit he/she gets from miner optimization and what benefits from timings.
I thinks Elio's utility will help to understand what timings you apply when "tuning" ))
Nevertheless, thanks for hard work, I'm still using your miner for older cards. But for vegas teamred is the king now.
I think you are wrong, the user doesn't have to know how things work, the user just needs to get out as much as possible from his mining hardware. The curious ones who want to learn how stuff works will learn. Also 1% of people want to know how the various timing parameters work, the other 99% just wants everything prepared so they can copy paste. Sometimes even that is too much work for them. And i am glad you shared what's your favorite miner, or who's da king with me, thank you  Does your miner return back stock timings when it exits? Sorry, no time to check it by myself on the rig |
|
|
|
|
90
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.4.4 - Cryptonight Thread - High hashrate, Low Power
|
on: April 19, 2019, 02:35:10 PM
|
Is it better to flash vega 56 with 64 bios or stay with original one ( VEGA 56 reference BlowER ).
Some of them are already hard to get stable ( 1407clock /900 mem : 930 mV for the bad ones)
I’ve had all my ref V56 flashed to V64 for such a long time now, I honestly can’t say much about stock 56 bios with Samsung HBM. I think you should try it though. The mem voltage is actually hardcoded in the bios, the names in eg OverdriveNTool are misnomers. The V64 bios drives mem with a higher voltage, so you might have a better (mem) experience. Just save the old bios and you can revert in a matter of minutes. Reference vegas have dual bios, so to go back you only need to switch bios position jumper |
|
|
|
|
92
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.4.3 - Cryptonight Thread - High hashrate, Low Power
|
on: April 18, 2019, 11:05:26 PM
|
Team Red Miner v0.4.4 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.4.4 - Added * mode specifically for modded timings on Vega GPUs. Use with e.g. --cn_config=15*15. This mode is now the default for Vegas.
- Introduced slow start/ramp-up. Threads increase their workload slowly at start or restart after e.g. a network outage.
- Added interleave adjustment logic. Readjusts the two threads per gpu over time to make sure they don't gravitate and get stuck.
- Added support for forcing colors (--force_color) for windows redirected consoles (git bash, cygwin, node.js).
- Added hotkey menu system (show stats, enable/disable gpu).
The new * mode opens up tweaking Vega timings for 2MB CN algos like CN-R! We've seen a few extremely tuned V64 LCs able to hit over 2400h/s on CN-R with 1400/1100 clocks! For those of you playing with timings, please share your results! We love seeing how far you guys can push these cards Max I got is 2470h/s with vega64lc 1428/1140@880mv and 147watt gpu power - all according to gpu-z. Not worth it )) 2390h/s at 1320/1100@825mv and 127watt is better I think Or even better vega56 (both samsung and hynix) 2100h/s at 1220/940@775mv and 97watt in gpu-z |
|
|
|
|
93
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: AMD Mem Tweak - Read/modify mem timings on the fly - [Vega Friendly] [Win/Linux]
|
on: April 18, 2019, 10:43:53 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). It’s 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: we’ve 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. It’s 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, there’s 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 |
|
|
|
|
94
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: AMD Mem Tweak - Read/modify mem timings on the fly - [Vega Friendly] [Win/Linux]
|
on: April 18, 2019, 08:02:29 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). It’s 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: we’ve 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) |
|
|
|
|
95
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: AMD Mem Tweak - Read/modify mem timings on the fly - [Vega Friendly] [Win/Linux]
|
on: April 18, 2019, 06:06:15 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). It’s 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 ) |
|
|
|
|
96
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: AMD Mem Tweak - Read/modify mem timings on the fly - [Vega Friendly] [Win/Linux]
|
on: April 18, 2019, 05:25:47 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). It’s 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 |
|
|
|
|
98
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: AMD Mem Tweak - Read/modify mem timings on the fly - [Vega Friendly] [Win/Linux]
|
on: April 17, 2019, 08:45:07 AM
|
guys. this crazy high --ref values you are using can't be good. check your pool-side hash ...
Why? if temps are low enough, data is more stable, and refreshes can be less frequent. Stock setting is almost certainly tuned to gaming usage under expectation of super high temps, plus a healthy margin. And if the setting is too high, it should manifest in mem errors and/or invalid results due to bit flips - no need to look at pool rate. FYI, my pool rate is as expected (w/ --REF 15600) the higher --ref value for my cards is 12800 for vega56 pulse hynix runnung 940mhz mem. All samsung cards are running below 10000 --ref. With higher values I got hashrate drops, dead gpu in teamred, hw errors or inconsistent hash. All my cards are tuned to run 50-53 degrees gpu temp, it is 60-65 degrees hbm temp according to gpu-z. vega56 cards are downvolted to 800mv (~775mv in gpu-z). vega64 cards with higher soc clock for higher mem clock are downvolted to 825mv (~800mv in gpu-z) vega56s are doing 20.5kh/s, vega64s are doing 21.2-21.6 kh/s. What temps are you running to handle this --ref 15600 values? Or are you using low intensity settings such as L18 for teamred to compensate it? |
|
|
|
|
Show Posts
