Bitcoin Forum
December 14, 2018, 11:03:16 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 »
  Print  
Author Topic: [ANN] TeamRedMiner 0.3.8 - CNv8 - Vega 64 2200+h/s Rx470 1025+h/s Low Power Draw  (Read 19314 times)
todxx
Member
**
Offline Offline

Activity: 95
Merit: 36


View Profile
October 30, 2018, 06:07:01 AM
Merited by scryptr (10), CjMapope (5), alucard20724 (1), PIOUPIOU99 (1), N2DCRYPT (1)
 #1

teamredminer v0.3.8 Beta Release
This is an optimized miner for AMD GPUs created by todxx and kerney666.

For questions/comments about lyra2z or phi2, please post in this thread.
This is the CNv8 thread for this miner.

This is a BETA release and may be unstable on some hardware.

Algorithms: cryptonight v8 (cnv2), lyra2z, phi2

GPUs Supported and Tested:
  • RX 580/570/480/470 on windows and linux with rocm or amdgpu-pro drivers
  • RX Vega 64/56, Vega FE on windows and linux with rocm or amdgpu-pro/PAL drivers
  • RX 560/550 on windows and linux with rocm or amdgpu-pro drivers

Windows download available here: https://github.com/todxx/teamredminer/releases/download/v0.3.8/teamredminer-v0.3.8-win.zip
Linux download available here: https://github.com/todxx/teamredminer/releases/download/v0.3.8/teamredminer-v0.3.8-linux.tgz
Brief readme available here: https://github.com/todxx/teamredminer

API: The miner includes a read-only api based on the sgminer-5.5 API.
Both the json and text formats are supported. For more details, we refer to the sgminer api documentation.

Software Requirements:
  • Supported GPU driver (see GPUs Supported above)
  • For cryptonight v8 on linux, only amdgpu-pro drivers are supported. Version 18.30 or newer is needed for Vegas. ROCm is not supported.

This miner includes the following dev fees:
  • Cryptonight v8: 2.5%
  • Lyra2z: 3%
  • Phi2: 3%

For reporting bugs and/or for features requests please make a post here and we'll do our best to respond.
Any feedback would be appreciated.

Features In Development:
  • New Algorithms
  • Pool Failover
  • Colors

Changes in v0.3.8
  • Added support for fan speed and temperatures.
  • Added watchdog function for gpu init stuck, dead gpu, over-temp gpu, and non-responding pool.
  • Added new optional 'L' config prefix for low-end cards like lexa/baffin for a 10+% speed-up on some cards
  • Added an option for writing out a log file.
  • Added cycling through multi-entry dns records when connecting to pools.
  • Added a pool-connect timeout.
  • Added measurement and displaying of pool response times.
  • Added support for 80-byte headers for Phi2 algo (for non-LUX coins).
  • Slightly tuned the '+' mode for polaris, some GPUs will show slight performance increase.
  • Fixed bug with API interface occasionally getting stuck.

Changes in v0.3.7
  • Redesigned GPU initialization, should now be less error prone.
  • Added clean shutdown to reduce driver/GPU crashes.
  • Added staggered GPU start-up to reduce GPU crashes.
  • Added CPU verification for CNv8 and associated --no_cpu_check option.
  • Fixed crash on pool authentication error.
  • Added --pool_broken_rpc work-around option for pools that violate json rpc spec.
  • Added option to reorder by PCIe bus numbers.
  • Added --list_devices option to show available devices.
  • Added changed stats formatting to indicate which numbers are accepted/rejected/hw-error shares.
  • Added uptime to stats.

Changes in v0.3.6
  • Added support for Rx550 cards (gfx804).
  • Improved stability on larger rigs, especially with weaker cpus.
  • Improved error reporting on failed initialization.

Changes in v0.3.5
  • Changed GPU initialization to be sequential by default and added --init_style option for faster init styles.
  • Fixed network buffer size issue preventing the use of very long usernames/passwords/rig_ids.
  • Added opencl platform auto-detection for AMD platforms when --platform is not specified.

Changes in v0.3.4
  • Added CryptoNight v8 (CNv2) support
  • Changed stats display to include pool hashrate and better formatting
  • Added parallel GPU initialization
  • Added output of submitted/accepted/rejected shares.
  • Changed hashrate reported to be full GPU hashrate (previously hashrate reported was after dev fee deduction)

Changes in v0.3.3
  • ROCm support reintroduced
  • API support based on the sgminer API
  • Improved GPU platform detection
  • PCIe bus id printed on startup and is available over API
  • Added option for periodic stats interval

Changes in v0.3.2
  • Added windows support/build
  • Added vega PAL driver support
  • Removed ROCm support (temporarily)
  • Removed libjansson dependency

Changes in v0.3.1
  • Fixed phi2 issues with rejected shares and low pool-side hashrate.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1544828596
Hero Member
*
Offline Offline

Posts: 1544828596

View Profile Personal Message (Offline)

Ignore
1544828596
Reply with quote  #2

1544828596
Report to moderator
kerney666
Member
**
Offline Offline

Activity: 154
Merit: 21


View Profile
October 30, 2018, 06:07:29 AM
Merited by scryptr (10), dragonmike (10)
 #2

This is the tuning guide included in the release, posting it here as well for people to read before they download.

A noteworthy fact not mentioned below is that we also asked two forum members not affiliated with us in any way, dragonmike and N2DCRYPT, to verify the miner hashrates for us on their rigs in an early test release. If someone asks, I'm sure they will present their own benchmarks. Imho, their results were in line with our own testing presented below.


Team Red Miner CNv8 Tuning

Background

This miner is more lean than other CN miners. This can translate into either increased hashrate, lower power draw, or both, or none of the above. Your mileage may vary and is highly dependent on mem straps and clocks. If running at the same hashrate as other CN miners, you can expect your power draw to decrease between -5-20W per gpu depending on gpu model and clocks.

To enable a higher hashrate, this miner generally requires a higher _core clk_ than normally used in CN mining. Unless you go nuts, your power draw will most probably be lower than that of other miners at lower clocks in the end anyway. This is the only way to achieve a > 2200 h/s read on a Vega 64.

There are fewer controls in this miner than the standard CN miner. It always runs with two threads, and you control the intensity per thread in the range 1-16. Moreover, you can choose between two modes, + and -. The mode will most often not have any effect on the end result, but it never hurts to try it.

Tuning guide

[Windows drivers]
For some Polaris cards, the good ol' blockchain driver works fine. However, the one driver that seems to be a good fit across the board is 18.6.1, and that's the driver we have used in all our Windows tests.

[Windows swap space]
You should to set up your swap space to be at least the sum of all GPU memory you intend to use when mining. Typically, for a 4GB card this is 3.5GB and for an 8GB it's 7.5GB. Playing it safe is recommended, i.e. rather add the full memory size of all your GPUs and set the swap to the total sum or more.

[Linux drivers]
You need the amdgpu-pro 18.30 drivers for your Vegas under linux to reach the max possible hashrate. Also, please note that this release does not include ROCm support for CNv8, it will be included in an upcoming release instead.

[Polaris cards (470-580)]
The standard configuration is 8+8 for all of these cards. 8+6 or 7+7 might give the same optimal hashrate, and 9+9 can, especially under linux, give a better result for 480/580. For some cards, 16+14 is the best choice but also increases the probability of stale shares. You must have good mem straps to reach a good hashrate. Normally e.g. the Pimp My Straps function in SRB Polaris Bios Editor is sufficient. For mem clk, boosting it as much as possible while avoiding mem errors is a good thing. The core clk should generally end up between 1230-1270. For 580s, a boosted core clk to 1300 can push the hashrate to 1100 h/s while still staying at a reasonable power draw. We have seen few Polaris cards not being able to reach 1020-1030 h/s with this miner when the proper mem straps are in place.

[Baffin and Lexa Pro cards (550-560)]
From v0.3.8, this miner has now been better optimized for these smaller cards. The major additions are that the '+' mode has been optimized and a 'L' prefix mode designed for the smallest Lexa Pro cards has been added. Some rules of thumb when you optimize your rigs:

  • We'd expect 4+4 and 4+3 to be the only interesting configs for 4GB cards.
  • For Lexa Pro cards with 8 CUs, prefix your config with 'L', i.e. L4+3.
  • The 'L' prefix is designed for Lexa Pro, but can also work well for Baffin with 10 CUs.
  • Many 2GB Lexa Pro can't do L4+3 under Win, only L3+3. For max performance you should try Linux and L4+3.
  • For an overkill full range test, you should try all of 4+4,4+3,3+3,3+2,2+2 in four modes: X+Y,LX+Y,X-Y,LX-Y

[Vega cards]
The Vegas can end up anywhere from 1900-2270 depending on if it's a 56 or 64, a reference card or not and your choice of clocks. The interesting configurations to try for your Vega are 14+14, 14-14, 15+15, 16+14. You can also try 16+15, 15+14, etc. The mem clk is very important, and you should aim for as high as possible while keeping your rig stable. If you have a Vega 64, please don't be shy to try a higher core clk. The 16+14 configuration will often not show its true capability before hitting 1500 core clk. Your power draw should still stay reasonable (as in lower than other miners at more standard clocks). For a lower core clk around 1408, some cards do best with 16+14, others with 15+15, some with 14+14, YMMV.

[Older cards]
We're sorry, we only support 470-580, 550/560 and Vega cards.

Benchmark results

For most Polaris cards below, one-click Pimp My Straps in SRB Polaris Bios Editor has been used for mem straps.

[6 x Rx 470 8GB (Samsung mem) rig]
8+8, 1250/900 cclk, 2000/900 mclk, 6105 h/s, total rig 685W

[Rx 560 4GB]
4+4, 1230/900 cclk, 2000/900 mclk, 540 h/s, unknown power draw

[Rx 570 8GB (Samsung mem)]
8+8, 1270/900 cclk, 2100/900 mclk, 1030 h/s @ ~100W at wall

[Rx 580 8GB (Hynix mem)]
8+8, 1250/900 cclk, 2000/900 mclk, 1029 h/s @ ~105W at wall

[Vega 56 reference card (56 bios, ppt mod)]
16+14, 1413/880 cclk, 935/880 mclk, ~2000 h/s @ ~197W at wall

[Vega 64 liquid cooling]
15+15, 1408/880 cclk, 1100/880 mclk, ~2100 h/s @ ~190W(?) at wall
16+14, 1560/925 cclk, 1100/880 mclk, ~2270 h/s @ ~210W(?) at wall

Example command lines

[Windows, one Vega 64 and one Rx580]
teamredminer.exe -a cnv8 -o stratum+tcp://pool.somexmrpool.com:7777 -u <wallet> -p MyWorker -d 0,1 --cn_config 16+14,8+8

[Linux, rig of 6 x Rx480 with different settings, not very realistic]
./teamredminer -a cnv8 -o stratum+tcp://pool.somexmrpool.com:7777 -u <wallet> -p MyWorker -d 0,1,2,3,4,5 --cn_config 8+8,7+7,9+9,8+8,8+8,9+9
rubine2323
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
October 30, 2018, 07:05:28 AM
 #3

Great to see some work from you again!

Ive just tested it real quick on my Vega and 470 Rig.
The power consumption is amazing!

Vega 56 2016H/s @ 164 Watts
RX 470 1008H/s @ 126 Watts

Crazy stuff. Ill have to do some more tests.

Unfortunately i dont have any merit points left  Angry
fluxy12
Jr. Member
*
Offline Offline

Activity: 102
Merit: 1


View Profile
October 30, 2018, 07:16:01 AM
 #4

Hello tested on windows 10 with 6*RX580, it doesn't launch unfortunatly. i tryed without Antivirus and without OC.

I got the message "failed to list OpenCL devices".

Can it be a driver problem ? i have blockchain drivers.

Thank you
rubine2323
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
October 30, 2018, 07:31:40 AM
 #5

Hello tested on windows 10 with 6*RX580, it doesn't launch unfortunatly. i tryed without Antivirus and without OC.

I got the message "failed to list OpenCL devices".

Can it be a driver problem ? i have blockchain drivers.

Thank you


Add to your batch file:

--platform=1
todxx
Member
**
Offline Offline

Activity: 95
Merit: 36


View Profile
October 30, 2018, 08:28:15 AM
 #6

Great to see some work from you again!

Ive just tested it real quick on my Vega and 470 Rig.
The power consumption is amazing!

Vega 56 2016H/s @ 164 Watts
RX 470 1008H/s @ 126 Watts

Crazy stuff. Ill have to do some more tests.

Unfortunately i dont have any merit points left  Angry

Thanks rubine!  It's been quite the push to get this release out.  Thanks for giving it a spin so quickly.
Your RX 470 power is a bit higher than what we've been seeing, what clocks are you running on it?

Hello tested on windows 10 with 6*RX580, it doesn't launch unfortunatly. i tryed without Antivirus and without OC.

I got the message "failed to list OpenCL devices".

Can it be a driver problem ? i have blockchain drivers.

Thank you


Hi flux,
As rubine mentioned, it's likely that you have more than one opencl platform, and the miner uses the first platform by default.
If adding the --platform=1 option that rubine suggested doesn't work, could you run clinfo on the command line and post the output?
dragonmike
Hero Member
*****
Offline Offline

Activity: 854
Merit: 530



View Profile
October 30, 2018, 09:27:53 AM
 #7

I tested this last night on two rigs (RX570's and Vega 56's).
Great work indeed. It's hands down the fastest and least power-consuming CN miner around.

For everyone's benefit, I got most hashrate using --cn_config=7+7 on the 570's and 16+14 on the Vegas so far, for virtually no increase in power draw. Net net a gain of about 4% hashrate at 7% less power than SRBminer.

Well done.

EDIT: looking forward to you releasing the same sort of improvements on the other CN variants (heavy/heaven/fast etc) and other algos that are grossly unoptimised for AMD hardware (looking at you x16r)!  Wink


░░░░░░░░░░░░░░░███████████████░░░░░░░░░░
░░░░░░░░░░░░██████████████████████░░░░░░
░░░░░░░░░░░█████████████████████████░░░░
░░░░░░░░░█████████░░░░░░░░░░░████████░░░
░░░░░░░░███████░░░░░░░░░░░░░░░░███████░░
░░░░░░░███████░░░░░░░░░░░░░░░░░░░█████░░
░░░░░░░███████░░░░░░░░░░░░░█████░██████░
░░░░░░░██████░░░░░█░░░░░████████░██████░
░░░░░░░███████░░░███░░░████░░███░██████░
░░░░░░░███████░░██░██░████░░███░░█████░░
░░░░░░░░██████░░██░░█░███░░███░░██████░░
░░░░░░░░░███████░██░█░█░░░███░░██████░░░
░░░░░░░░░░░██████░███░░░███░░░█████░░░░░
░░░░░░░░░██░░████░░░░░░██░░░██████░░░░░░
░░░░░░░░████░░░░░██████░░░█████░░░░░░░░░
░░░░░░░░███████░░░░░░░░░███░░░░░░░░░░░░░
░░░░░░░░░░░█████████████░░░░░░░░░░░░░░░░
░░░░░░░░███░░░█████░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░██████░░░███░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░██████░░░░░░░░░░░░░░░░░░░░░░░
▂▂ ▃▃ ▅ ▆ ▇ █ TeraWATT █ ▇ ▆ ▅ ▃▃ ▂▂
Global LED Adoption Through Blockchain Technology
≒≒≒≒≒≒≒≒≒『ICO IS LIVE』≒≒≒≒≒≒≒≒≒
WEBSITE』『WHITEPAPER
≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒
TWITTER』『TELEGRAM
netto7
Jr. Member
*
Offline Offline

Activity: 98
Merit: 2


View Profile
October 30, 2018, 09:53:21 AM
 #8

have plan to add more algo?

╭═══════ Petlife ═══════╮
│    Blockchain in veterinary medicine    │
╰════ https://icopet.life/ ════╯
stolarzz
Newbie
*
Offline Offline

Activity: 59
Merit: 0


View Profile
October 30, 2018, 10:05:08 AM
 #9

820kh/s for Nitro+ 570 4Gb it's optimal?
Is there a possibility to hash 1k+ with this card?
dragonmike
Hero Member
*****
Offline Offline

Activity: 854
Merit: 530



View Profile
October 30, 2018, 10:08:21 AM
 #10

820kh/s for Nitro+ 570 4Gb it's optimal?
Is there a possibility to hash 1k+ with this card?
Have you modded your mem straps?
If not, do it. You should be getting over 1k easily with this card.


░░░░░░░░░░░░░░░███████████████░░░░░░░░░░
░░░░░░░░░░░░██████████████████████░░░░░░
░░░░░░░░░░░█████████████████████████░░░░
░░░░░░░░░█████████░░░░░░░░░░░████████░░░
░░░░░░░░███████░░░░░░░░░░░░░░░░███████░░
░░░░░░░███████░░░░░░░░░░░░░░░░░░░█████░░
░░░░░░░███████░░░░░░░░░░░░░█████░██████░
░░░░░░░██████░░░░░█░░░░░████████░██████░
░░░░░░░███████░░░███░░░████░░███░██████░
░░░░░░░███████░░██░██░████░░███░░█████░░
░░░░░░░░██████░░██░░█░███░░███░░██████░░
░░░░░░░░░███████░██░█░█░░░███░░██████░░░
░░░░░░░░░░░██████░███░░░███░░░█████░░░░░
░░░░░░░░░██░░████░░░░░░██░░░██████░░░░░░
░░░░░░░░████░░░░░██████░░░█████░░░░░░░░░
░░░░░░░░███████░░░░░░░░░███░░░░░░░░░░░░░
░░░░░░░░░░░█████████████░░░░░░░░░░░░░░░░
░░░░░░░░███░░░█████░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░██████░░░███░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░██████░░░░░░░░░░░░░░░░░░░░░░░
▂▂ ▃▃ ▅ ▆ ▇ █ TeraWATT █ ▇ ▆ ▅ ▃▃ ▂▂
Global LED Adoption Through Blockchain Technology
≒≒≒≒≒≒≒≒≒『ICO IS LIVE』≒≒≒≒≒≒≒≒≒
WEBSITE』『WHITEPAPER
≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒
TWITTER』『TELEGRAM
stolarzz
Newbie
*
Offline Offline

Activity: 59
Merit: 0


View Profile
October 30, 2018, 10:16:06 AM
 #11

820kh/s for Nitro+ 570 4Gb it's optimal?
Is there a possibility to hash 1k+ with this card?
Have you modded your mem straps?
If not, do it. You should be getting over 1k easily with this card.
They were modded long time ago for eth the card is getting 30+mh avarage there, is there any difference for cryptonight?
dragonmike
Hero Member
*****
Offline Offline

Activity: 854
Merit: 530



View Profile
October 30, 2018, 10:17:21 AM
 #12

820kh/s for Nitro+ 570 4Gb it's optimal?
Is there a possibility to hash 1k+ with this card?
Have you modded your mem straps?
If not, do it. You should be getting over 1k easily with this card.
They were modded long time ago for eth the card is getting 30+mh avarage there, is there any difference for cryptonight?
Not much.
Have you tried using --cn_config=7+7 ?


░░░░░░░░░░░░░░░███████████████░░░░░░░░░░
░░░░░░░░░░░░██████████████████████░░░░░░
░░░░░░░░░░░█████████████████████████░░░░
░░░░░░░░░█████████░░░░░░░░░░░████████░░░
░░░░░░░░███████░░░░░░░░░░░░░░░░███████░░
░░░░░░░███████░░░░░░░░░░░░░░░░░░░█████░░
░░░░░░░███████░░░░░░░░░░░░░█████░██████░
░░░░░░░██████░░░░░█░░░░░████████░██████░
░░░░░░░███████░░░███░░░████░░███░██████░
░░░░░░░███████░░██░██░████░░███░░█████░░
░░░░░░░░██████░░██░░█░███░░███░░██████░░
░░░░░░░░░███████░██░█░█░░░███░░██████░░░
░░░░░░░░░░░██████░███░░░███░░░█████░░░░░
░░░░░░░░░██░░████░░░░░░██░░░██████░░░░░░
░░░░░░░░████░░░░░██████░░░█████░░░░░░░░░
░░░░░░░░███████░░░░░░░░░███░░░░░░░░░░░░░
░░░░░░░░░░░█████████████░░░░░░░░░░░░░░░░
░░░░░░░░███░░░█████░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░██████░░░███░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░██████░░░░░░░░░░░░░░░░░░░░░░░
▂▂ ▃▃ ▅ ▆ ▇ █ TeraWATT █ ▇ ▆ ▅ ▃▃ ▂▂
Global LED Adoption Through Blockchain Technology
≒≒≒≒≒≒≒≒≒『ICO IS LIVE』≒≒≒≒≒≒≒≒≒
WEBSITE』『WHITEPAPER
≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒
TWITTER』『TELEGRAM
stolarzz
Newbie
*
Offline Offline

Activity: 59
Merit: 0


View Profile
October 30, 2018, 10:19:49 AM
 #13

Quote
Have you tried using --cn_config=7+7 ?
Yup there is no change at all. All my AMD's are 4GB and never get more than 820kh with cryptonight Sad
dragonmike
Hero Member
*****
Offline Offline

Activity: 854
Merit: 530



View Profile
October 30, 2018, 10:27:15 AM
 #14

what clocks?


EDIT: sidenote... for the lulz I increased clock speeds on the Vega56's to 1590... Hashrate went up to 2150 h/s!  Grin
But power went up quite massively as well (over 225W per GPU).


░░░░░░░░░░░░░░░███████████████░░░░░░░░░░
░░░░░░░░░░░░██████████████████████░░░░░░
░░░░░░░░░░░█████████████████████████░░░░
░░░░░░░░░█████████░░░░░░░░░░░████████░░░
░░░░░░░░███████░░░░░░░░░░░░░░░░███████░░
░░░░░░░███████░░░░░░░░░░░░░░░░░░░█████░░
░░░░░░░███████░░░░░░░░░░░░░█████░██████░
░░░░░░░██████░░░░░█░░░░░████████░██████░
░░░░░░░███████░░░███░░░████░░███░██████░
░░░░░░░███████░░██░██░████░░███░░█████░░
░░░░░░░░██████░░██░░█░███░░███░░██████░░
░░░░░░░░░███████░██░█░█░░░███░░██████░░░
░░░░░░░░░░░██████░███░░░███░░░█████░░░░░
░░░░░░░░░██░░████░░░░░░██░░░██████░░░░░░
░░░░░░░░████░░░░░██████░░░█████░░░░░░░░░
░░░░░░░░███████░░░░░░░░░███░░░░░░░░░░░░░
░░░░░░░░░░░█████████████░░░░░░░░░░░░░░░░
░░░░░░░░███░░░█████░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░██████░░░███░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░██████░░░░░░░░░░░░░░░░░░░░░░░
▂▂ ▃▃ ▅ ▆ ▇ █ TeraWATT █ ▇ ▆ ▅ ▃▃ ▂▂
Global LED Adoption Through Blockchain Technology
≒≒≒≒≒≒≒≒≒『ICO IS LIVE』≒≒≒≒≒≒≒≒≒
WEBSITE』『WHITEPAPER
≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒≒
TWITTER』『TELEGRAM
rubine2323
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
October 30, 2018, 10:52:33 AM
 #15

Great to see some work from you again!

Ive just tested it real quick on my Vega and 470 Rig.
The power consumption is amazing!

Vega 56 2016H/s @ 164 Watts
RX 470 1008H/s @ 126 Watts

Crazy stuff. Ill have to do some more tests.

Unfortunately i dont have any merit points left  Angry

Thanks rubine!  It's been quite the push to get this release out.  Thanks for giving it a spin so quickly.
Your RX 470 power is a bit higher than what we've been seeing, what clocks are you running on it?

Hello tested on windows 10 with 6*RX580, it doesn't launch unfortunatly. i tryed without Antivirus and without OC.

I got the message "failed to list OpenCL devices".

Can it be a driver problem ? i have blockchain drivers.

Thank you


Hi flux,
As rubine mentioned, it's likely that you have more than one opencl platform, and the miner uses the first platform by default.
If adding the --platform=1 option that rubine suggested doesn't work, could you run clinfo on the command line and post the output?

Current clk at 1250@900, 2000@900. My bios mod may differ a bit.
vmozara
Member
**
Offline Offline

Activity: 170
Merit: 50


View Profile
October 30, 2018, 11:00:32 AM
 #16

this looks promising.

Especially in a sea of viruses and trojan miners that we had here. I wish i had any lefover merit to give to you Smiley

I tested at my home PC and now i will proceed to update my rigs. It seems your dev fee is high but it is well deserved.

Test at home PC: Adrenalin 18.10.2, win 10 1809, vega 64 custom cooling, power table 85% from vega guide (unfortunate vega), core 1550/900 mem 1150/900

All consumption below is entire system consumption from the wall

JCE miner: 2080H/s @ 300W
SRBminer: 2130H/s @ 300W
TeamRedMiner: 2300H/s @ 285W

 Shocked

I will provide here results from optimized Vega rigs later on.

Is there any special driver version you recommend for Vega?

Thanks!
N2DCRYPT
Jr. Member
*
Offline Offline

Activity: 106
Merit: 3


View Profile
October 30, 2018, 11:06:04 AM
 #17

Posting to confirm that the advertised hashrates and power draws for this miner are legitimate. Quite an impressive release from kerney666 and todxx; personally, I've had issues switching over rigs to v8 because of the increased power draw, and this miner has alleviated those problems, while giving increased hashrate!

My Vega 64s are currently working at about 2100 H/s and Vega 56's are running 2000 H/s with lower power draw and higher hashrates than I was running on SRBMiner.
dafuzz_rsa
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
October 30, 2018, 11:06:22 AM
 #18

Absolutely amazing results. Well done!
Looking forward to seeing what else you guys have to offer
N2DCRYPT
Jr. Member
*
Offline Offline

Activity: 106
Merit: 3


View Profile
October 30, 2018, 11:08:48 AM
 #19


Is there any special driver version you recommend for Vega?


Vmozara, the Adrenalin 18.6.1 drivers should work well; and that's what I'm running on all of mine--anything older than that tends to have problems with v8.
todxx
Member
**
Offline Offline

Activity: 95
Merit: 36


View Profile
October 30, 2018, 11:54:04 AM
 #20

I tested this last night on two rigs (RX570's and Vega 56's).
Great work indeed. It's hands down the fastest and least power-consuming CN miner around.

For everyone's benefit, I got most hashrate using --cn_config=7+7 on the 570's and 16+14 on the Vegas so far, for virtually no increase in power draw. Net net a gain of about 4% hashrate at 7% less power than SRBminer.

Well done.

EDIT: looking forward to you releasing the same sort of improvements on the other CN variants (heavy/heaven/fast etc) and other algos that are grossly unoptimised for AMD hardware (looking at you x16r)!  Wink

Thanks for helping with the early testing dragonmike!  It really helps to have some outside validation of our numbers as a bit of a sanity check before a release Smiley
As for CN variants and other new algos, we will be adding more, but it may be a little while.  This last push to get CNv8 from the drawing board and into production has taken over a month of full time work on both our parts and we both need a bit of a breather after this one.  That said, adding CN variants now that we have the general CN infrastructure in place should be much easier.  We've also done some very initial work on x16r and it looks like there's plenty of room for improvement, but at this point we can't make any promises on what we'll be able to release and when.

what clocks?


EDIT: sidenote... for the lulz I increased clock speeds on the Vega56's to 1590... Hashrate went up to 2150 h/s!  Grin
But power went up quite massively as well (over 225W per GPU).

Haha, I just spent a couple hours pushing my Vega FE too.  I managed to hit just over 2400h/s running at 1610MHz core and 1195MHz mem clocks!  Grin  The card was pulling about 300W alone so not very useful, but I love seeing that 2400h/s readout!

Quote
Have you tried using --cn_config=7+7 ?
Yup there is no change at all. All my AMD's are 4GB and never get more than 820kh with cryptonight Sad

Do you know what type of memory is on your card?
I have some MSI RX470 mining edition cards that have Micron memory and so far I can only get them to about 850h/s with the best straps I could find.

this looks promising.

Especially in a sea of viruses and trojan miners that we had here. I wish i had any lefover merit to give to you Smiley

I tested at my home PC and now i will proceed to update my rigs. It seems your dev fee is high but it is well deserved.

Test at home PC: Adrenalin 18.10.2, win 10 1809, vega 64 custom cooling, power table 85% from vega guide (unfortunate vega), core 1550/900 mem 1150/900

All consumption below is entire system consumption from the wall

JCE miner: 2080H/s @ 300W
SRBminer: 2130H/s @ 300W
TeamRedMiner: 2300H/s @ 285W

 Shocked

I will provide here results from optimized Vega rigs later on.

Is there any special driver version you recommend for Vega?

Thanks!

Thanks vmozara!  Nice to see someone else out there pushing the higher 2300+ hashrates  Smiley
As for the driver version, we have done most of our testing on 18.6.1, so I would consider that the safest bet.  I believe kerney saw some issues with Vegas running the old blockchain drivers, so I would avoid those for Vegas.

Posting to confirm that the advertised hashrates and power draws for this miner are legitimate. Quite an impressive release from kerney666 and todxx; personally, I've had issues switching over rigs to v8 because of the increased power draw, and this miner has alleviated those problems, while giving increased hashrate!

My Vega 64s are currently working at about 2100 H/s and Vega 56's are running 2000 H/s with lower power draw and higher hashrates than I was running on SRBMiner.

Thanks for helping with the early testing N2DCRYPT!  We really appreciate you taking the time to kick the tires before the release!
Also I'm glad we could help get your rigs back into their old power profiles Smiley

Absolutely amazing results. Well done!
Looking forward to seeing what else you guys have to offer

Thanks dafuzz_rsa!  We're looking forward to cranking out some new algos after we take a little bit of a breather Smiley
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!