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.
Topic: [ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More - page 150. (Read 211432 times)
October 30, 2018, 07:06:04 AM
October 30, 2018, 07:00:32 AM
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
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
I will provide here results from optimized Vega rigs later on.
Is there any special driver version you recommend for Vega?
Thanks!
Especially in a sea of viruses and trojan miners that we had here. I wish i had any lefover merit to give to you
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
I will provide here results from optimized Vega rigs later on.
Is there any special driver version you recommend for Vega?
Thanks!
October 30, 2018, 06:52:33 AM
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
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
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
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.
October 30, 2018, 06:27:15 AM
what clocks?
EDIT: sidenote... for the lulz I increased clock speeds on the Vega56's to 1590... Hashrate went up to 2150 h/s!
But power went up quite massively as well (over 225W per GPU).
EDIT: sidenote... for the lulz I increased clock speeds on the Vega56's to 1590... Hashrate went up to 2150 h/s!
But power went up quite massively as well (over 225W per GPU).
October 30, 2018, 06:19:49 AM
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 
October 30, 2018, 06:17:21 AM
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?Is there a possibility to hash 1k+ with this card?
If not, do it. You should be getting over 1k easily with this card.
Have you tried using --cn_config=7+7 ?
October 30, 2018, 06:16:06 AM
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?Is there a possibility to hash 1k+ with this card?
If not, do it. You should be getting over 1k easily with this card.
October 30, 2018, 06:08:21 AM
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?Is there a possibility to hash 1k+ with this card?
If not, do it. You should be getting over 1k easily with this card.
October 30, 2018, 06:05:08 AM
820kh/s for Nitro+ 570 4Gb it's optimal?
Is there a possibility to hash 1k+ with this card?
Is there a possibility to hash 1k+ with this card?
October 30, 2018, 05:53:21 AM
have plan to add more algo?
October 30, 2018, 05:27:53 AM
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)!
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)!
October 30, 2018, 04:28:15 AM
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
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
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
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?
October 30, 2018, 03:31:40 AM
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
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
October 30, 2018, 03:16:01 AM
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
I got the message "failed to list OpenCL devices".
Can it be a driver problem ? i have blockchain drivers.
Thank you
October 30, 2018, 03:05:28 AM
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
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
October 30, 2018, 02:07:29 AM
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:
[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 -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 -p MyWorker -d 0,1,2,3,4,5 --cn_config 8+8,7+7,9+9,8+8,8+8,9+9
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
[Linux, rig of 6 x Rx480 with different settings, not very realistic]
./teamredminer -a cnv8 -o stratum+tcp://pool.somexmrpool.com:7777 -u
October 30, 2018, 02:07:01 AM
teamredminer v0.10.10
This is an optimized miner for AMD GPUs and Xilinx FPGAs created by todxx and kerney666.
Download is available in the github releases section.
TRM official website: https://www.teamredminer.com
TRM discord server: https://discord.gg/RGykKqB
Below is a list of mining operating systems and management software that have built-in support for teamredminer:
This miner supports a range of algorithms. Please see the list below for details.
The miner is configured via command line only, please run with the --help option to print a short help message for how to use the command line options.
GPU Support
GPUs supported and tested:
- Navi - RX 5700(XT)/5600(XT)/5500(XT) for supported algos in the table below.
- Big Navi - RX 6900XT, RX 6800(XT), RX 6700(XT), RX6600XT - same support as for Navi.
- RDNA3 - 7900XT, 7900XTX, see Navi30 in the table below for supported algos.
- Vega - RX Vega 64/56, Vega FE, Radeon VII (Vega 2)
- Polaris - RX 580/480/570/470/560/460/550
- Fiji - R9 Fury/Fury X/Nano, MI8 (supported but with very limited testing).
- Tonga/Antigua - R9 285/285X/380/380X, W7100, S7150 (beta support from 0.8.2. Only ethash+kawpow available.)
Supported GPU algorithms and their respective dev fees:
| GPU Algorithm | Fee |
| Ethash on Polaris GPUs | 0.75% |
| Ethash on all other GPUs | 1.0% |
| Kawpow | 2.0% |
| Verthash | 2.0% |
| Autolykos2 | 2.0% |
| Ton | 1.0% |
| Kaspa | 1.0% |
| Ironfish | 1.0% |
| Nimiq | 2.5% |
| Cryptonight R | 2.5% |
| Cryptonight v8 upx2 | 2.5% |
| Cryptonight v8 turtle | 2.5% |
| Cryptonight v8 half | 2.5% |
| Cryptonight v8 double | 2.5% |
| Cryptonight v8 rwz | 2.5% |
| Cryptonight v8 | 2.5% |
| Cryptonight heavy | 2.5% |
| Cryptonight haven | 2.5% |
| Cryptonight saber | 2.5% |
| Cryptonight conceal | 2.5% |
| Chukwa-512 (Turtlecoin) | 2.5% |
| Chukwa-1024 (Turtlecoin) | 2.5% |
| x16r | 2.5% |
| x16rv2 | 2.5% |
| x16s | 2.5% |
| x16rt | 2.5% |
| MTP | 2.5% |
| Cuckatoo31 | 2.5% |
| Cuckarood29 | 2.5% |
| Lyra2rev3 | 2.5% |
| Lyra2z | 3.0% |
| Phi2 | 3.0% |
Some algorithms are not supported on some GPU architectures and/or drivers. Below is the compatiblity table:
Navi30
Jump to:
|