deadsix
|
|
November 05, 2018, 07:12:59 PM |
|
Hitting ~1000h/s on my RX 470's across memory types. Great job guys, repped++. Currently testing for stability and poolside reporting consistency.
|
|
|
|
heavyarms1912
|
|
November 05, 2018, 09:01:37 PM |
|
Some dirty oc results. RX570 8gb . 1396 core / 2275 memory. 1133 H/s.
|
|
|
|
ivomm
Legendary
Offline
Activity: 1901
Merit: 3171
All good things to those who wait
|
|
November 05, 2018, 11:57:57 PM |
|
I just tested this miner. So far stable with 1.8% increase of the profit. However it is liqudated by the same difference between the dev fee with the competitor miner. So, I will run it for a day to support the team, but I hope the fee will be reduced to have some advantage to chose this miner.
|
|
|
|
Bael
Jr. Member
Offline
Activity: 87
Merit: 2
|
|
November 06, 2018, 12:52:02 AM Last edit: November 06, 2018, 02:27:18 AM by Bael |
|
Hello I want to tune the cards, but there is something I do not understand. [Polaris cards (470-580)] The standard configuration is 8 + 8 for all of these cards. 7 + 7 might give the same optimal hash, 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. My default cards are like this: If I put 8 + 8 what does it mean? or if I put for example 7 + 7? When doing so, do I raise or lower the intensity of the gpu? Excuse me because it seems that it's obvious to everyone but I do not know what it means, basically I've mined eth always, I think I'm missing something xDD Great job TeamRedMiner! regards
|
|
|
|
golya87
Newbie
Offline
Activity: 10
Merit: 0
|
|
November 06, 2018, 01:43:16 AM |
|
Hello After I start the miner, I've got the following error. Team Red Miner version 0.3.6 [2018-11-06 02:26:05] Auto-detected AMD OpenCL platform 1 [2018-11-06 02:26:05] Initializing GPU 0. [2018-11-06 02:26:06] Pool gulf.moneroocean.stream login succeeded. [2018-11-06 02:26:06] Pool gulf.moneroocean.stream received new job. (job_id: BnhOxLVdmQh7rdyK3iFIaRD8iinZ) [2018-11-06 02:26:06] Pool gulf.moneroocean.stream set difficulty to 128001 [2018-11-06 02:26:07] Initializing GPU 1. [2018-11-06 02:26:07] Dev pool connected and ready. [2018-11-06 02:26:08] Initializing GPU 2. [2018-11-06 02:26:10] Initializing GPU 3. [2018-11-06 02:26:11] Initializing GPU 4. [2018-11-06 02:26:13] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 1: Vega with 56 CU (PCIe 03:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 2: Vega with 56 CU (PCIe 06:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 3: Vega with 56 CU (PCIe 13:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 4: Vega with 56 CU (PCIe 16:00.0) (CN 14+14) [2018-11-06 02:26:15] Pool gulf.moneroocean.stream received new job. (job_id: vCLrCaDLBkR++jmkZht+CinbJF4f) [2018-11-06 02:26:36] Stats GPU 0 - cnv8: 1.432kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 1 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 2 - cnv8: 1.419kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 3 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 4 - cnv8: 1.427kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats Total - cnv8: 7.122kh/s, avg 8.746kh/s, pool 0.0 h/s [2018-11-06 02:26:44] Pool gulf.moneroocean.stream connection was closed due to an error. [2018-11-06 02:26:44] Pool gulf.moneroocean.stream login succeeded. [2018-11-06 02:26:44] Pool gulf.moneroocean.stream received new job. (job_id: urc+A/g/16ZnWkFNtJIAmMZFqX0r) [2018-11-06 02:26:44] Pool gulf.moneroocean.stream set difficulty to 128001
This is my starting command: teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14 What did I wrong? Thank you in advance!
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 06, 2018, 04:02:27 AM |
|
Hello I want to tune the cards, but there is something I do not understand. [Polaris cards (470-580)] The standard configuration is 8 + 8 for all of these cards. 7 + 7 might give the same optimal hash, 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. My default cards are like this: If I put 8 + 8 what does it mean? or if I put for example 7 + 7? When doing so, do I raise or lower the intensity of the gpu? Excuse me because it seems that it's obvious to everyone but I do not know what it means, basically I've mined eth always, I think I'm missing something xDD Great job TeamRedMiner! regards Hi Bael! Thanks for the kind words. It is an intensity setting, like you suggest yourself. The sum of the two numbers will control your total memory consumption on the gpu and how it is spread out over the two threads per gpu. A 4GB card only do 7+7, maybe 8+7. 8 GB can do up to 15+15 or 16+14, but that's rarely worth it for Polaris cards, only Vegas.
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 06, 2018, 04:40:37 AM |
|
Hello After I start the miner, I've got the following error. Team Red Miner version 0.3.6 [2018-11-06 02:26:05] Auto-detected AMD OpenCL platform 1 [2018-11-06 02:26:05] Initializing GPU 0. [2018-11-06 02:26:06] Pool gulf.moneroocean.stream login succeeded. [2018-11-06 02:26:06] Pool gulf.moneroocean.stream received new job. (job_id: BnhOxLVdmQh7rdyK3iFIaRD8iinZ) [2018-11-06 02:26:06] Pool gulf.moneroocean.stream set difficulty to 128001 [2018-11-06 02:26:07] Initializing GPU 1. [2018-11-06 02:26:07] Dev pool connected and ready. [2018-11-06 02:26:08] Initializing GPU 2. [2018-11-06 02:26:10] Initializing GPU 3. [2018-11-06 02:26:11] Initializing GPU 4. [2018-11-06 02:26:13] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 1: Vega with 56 CU (PCIe 03:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 2: Vega with 56 CU (PCIe 06:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 3: Vega with 56 CU (PCIe 13:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 4: Vega with 56 CU (PCIe 16:00.0) (CN 14+14) [2018-11-06 02:26:15] Pool gulf.moneroocean.stream received new job. (job_id: vCLrCaDLBkR++jmkZht+CinbJF4f) [2018-11-06 02:26:36] Stats GPU 0 - cnv8: 1.432kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 1 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 2 - cnv8: 1.419kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 3 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 4 - cnv8: 1.427kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats Total - cnv8: 7.122kh/s, avg 8.746kh/s, pool 0.0 h/s [2018-11-06 02:26:44] Pool gulf.moneroocean.stream connection was closed due to an error. [2018-11-06 02:26:44] Pool gulf.moneroocean.stream login succeeded. [2018-11-06 02:26:44] Pool gulf.moneroocean.stream received new job. (job_id: urc+A/g/16ZnWkFNtJIAmMZFqX0r) [2018-11-06 02:26:44] Pool gulf.moneroocean.stream set difficulty to 128001
This is my starting command: teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14 What did I wrong? Thank you in advance! Hmm, hashing looks fine, it would rather be something in the rpc communication with Monero Ocean, although we haven't gotten any other reports for this pool. We're working on fixing some small rpc bugs, we'll make sure to test against Monero Ocean as well.
|
|
|
|
icebody
Newbie
Offline
Activity: 1
Merit: 0
|
|
November 06, 2018, 06:36:17 AM |
|
Just noted that Vega Frontier Edition is performing bad with different settings..... around 1980-2000 h/s any advice?
|
|
|
|
keksik
Jr. Member
Offline
Activity: 169
Merit: 1
|
|
November 06, 2018, 09:42:24 AM |
|
hello, i run it for many hours thru the day, and i am getting soo many rejected shares on one gpu is hashing 940h/s but getting like 6/345 shares, this is caused by what? also it wrote low difficulty share, rejected
|
|
|
|
Mashy81
Jr. Member
Offline
Activity: 225
Merit: 1
|
|
November 06, 2018, 09:46:20 AM |
|
hello, i run it for many hours thru the day, and i am getting soo many rejected shares on one gpu is hashing 940h/s but getting like 6/345 shares, this is caused by what? also it wrote low difficulty share, rejected
What are your settings. Core,memory and voltages. To high clocks and or too low voltage some times
|
|
|
|
Mashy81
Jr. Member
Offline
Activity: 225
Merit: 1
|
|
November 06, 2018, 09:48:59 AM |
|
Changed to static difficulty and it smoothed out the pool hash rate variance. Miner reports 10.2khs pool reports 10khs ave after 12hrs
|
|
|
|
vrottenberg
Jr. Member
Offline
Activity: 31
Merit: 2
|
|
November 06, 2018, 10:04:39 AM |
|
Dear dev, I really look forward to the function of the failover pool in pools.txt file!
|
|
|
|
keksik
Jr. Member
Offline
Activity: 169
Merit: 1
|
|
November 06, 2018, 10:30:02 AM |
|
hello, i run it for many hours thru the day, and i am getting soo many rejected shares on one gpu is hashing 940h/s but getting like 6/345 shares, this is caused by what? also it wrote low difficulty share, rejected
What are your settings. Core,memory and voltages. To high clocks and or too low voltage some times i tried to lower 25mhz memory, lets see..i havent seen any drops in core and voltage in hwinfo, just few memory errors(like 200 or so only)
|
|
|
|
Mashy81
Jr. Member
Offline
Activity: 225
Merit: 1
|
|
November 06, 2018, 11:30:57 AM |
|
hello, i run it for many hours thru the day, and i am getting soo many rejected shares on one gpu is hashing 940h/s but getting like 6/345 shares, this is caused by what? also it wrote low difficulty share, rejected
What are your settings. Core,memory and voltages. To high clocks and or too low voltage some times i tried to lower 25mhz memory, lets see..i havent seen any drops in core and voltage in hwinfo, just few memory errors(like 200 or so only) Ideally you want zero memory errors. Keep dropping little by little until no errors. Sometimes it appears as thought your hashrate is lower but it will be higher accepted buy the pool. Better effective hashrate is what you want
|
|
|
|
golya87
Newbie
Offline
Activity: 10
Merit: 0
|
|
November 06, 2018, 02:10:59 PM |
|
Hello After I start the miner, I've got the following error. Team Red Miner version 0.3.6 [2018-11-06 02:26:05] Auto-detected AMD OpenCL platform 1 [2018-11-06 02:26:05] Initializing GPU 0. [2018-11-06 02:26:06] Pool gulf.moneroocean.stream login succeeded. [2018-11-06 02:26:06] Pool gulf.moneroocean.stream received new job. (job_id: BnhOxLVdmQh7rdyK3iFIaRD8iinZ) [2018-11-06 02:26:06] Pool gulf.moneroocean.stream set difficulty to 128001 [2018-11-06 02:26:07] Initializing GPU 1. [2018-11-06 02:26:07] Dev pool connected and ready. [2018-11-06 02:26:08] Initializing GPU 2. [2018-11-06 02:26:10] Initializing GPU 3. [2018-11-06 02:26:11] Initializing GPU 4. [2018-11-06 02:26:13] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 1: Vega with 56 CU (PCIe 03:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 2: Vega with 56 CU (PCIe 06:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 3: Vega with 56 CU (PCIe 13:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 4: Vega with 56 CU (PCIe 16:00.0) (CN 14+14) [2018-11-06 02:26:15] Pool gulf.moneroocean.stream received new job. (job_id: vCLrCaDLBkR++jmkZht+CinbJF4f) [2018-11-06 02:26:36] Stats GPU 0 - cnv8: 1.432kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 1 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 2 - cnv8: 1.419kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 3 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 4 - cnv8: 1.427kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats Total - cnv8: 7.122kh/s, avg 8.746kh/s, pool 0.0 h/s [2018-11-06 02:26:44] Pool gulf.moneroocean.stream connection was closed due to an error. [2018-11-06 02:26:44] Pool gulf.moneroocean.stream login succeeded. [2018-11-06 02:26:44] Pool gulf.moneroocean.stream received new job. (job_id: urc+A/g/16ZnWkFNtJIAmMZFqX0r) [2018-11-06 02:26:44] Pool gulf.moneroocean.stream set difficulty to 128001
This is my starting command: teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14 What did I wrong? Thank you in advance! Hmm, hashing looks fine, it would rather be something in the rpc communication with Monero Ocean, although we haven't gotten any other reports for this pool. We're working on fixing some small rpc bugs, we'll make sure to test against Monero Ocean as well. I've get the same error with monero.miningpoolhub.com and wownero.ingest.cryptoknight.cc also. I've enabled the miner sw in the windows firewall rules also, so it shouldn't be a FW issue.
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 06, 2018, 02:29:03 PM |
|
Hello After I start the miner, I've got the following error. Team Red Miner version 0.3.6 [2018-11-06 02:26:05] Auto-detected AMD OpenCL platform 1 [2018-11-06 02:26:05] Initializing GPU 0. [2018-11-06 02:26:06] Pool gulf.moneroocean.stream login succeeded. [2018-11-06 02:26:06] Pool gulf.moneroocean.stream received new job. (job_id: BnhOxLVdmQh7rdyK3iFIaRD8iinZ) [2018-11-06 02:26:06] Pool gulf.moneroocean.stream set difficulty to 128001 [2018-11-06 02:26:07] Initializing GPU 1. [2018-11-06 02:26:07] Dev pool connected and ready. [2018-11-06 02:26:08] Initializing GPU 2. [2018-11-06 02:26:10] Initializing GPU 3. [2018-11-06 02:26:11] Initializing GPU 4. [2018-11-06 02:26:13] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 1: Vega with 56 CU (PCIe 03:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 2: Vega with 56 CU (PCIe 06:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 3: Vega with 56 CU (PCIe 13:00.0) (CN 14+14) [2018-11-06 02:26:13] Successfully initialized GPU 4: Vega with 56 CU (PCIe 16:00.0) (CN 14+14) [2018-11-06 02:26:15] Pool gulf.moneroocean.stream received new job. (job_id: vCLrCaDLBkR++jmkZht+CinbJF4f) [2018-11-06 02:26:36] Stats GPU 0 - cnv8: 1.432kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 1 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 2 - cnv8: 1.419kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 3 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats GPU 4 - cnv8: 1.427kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0 [2018-11-06 02:26:36] Stats Total - cnv8: 7.122kh/s, avg 8.746kh/s, pool 0.0 h/s [2018-11-06 02:26:44] Pool gulf.moneroocean.stream connection was closed due to an error. [2018-11-06 02:26:44] Pool gulf.moneroocean.stream login succeeded. [2018-11-06 02:26:44] Pool gulf.moneroocean.stream received new job. (job_id: urc+A/g/16ZnWkFNtJIAmMZFqX0r) [2018-11-06 02:26:44] Pool gulf.moneroocean.stream set difficulty to 128001
This is my starting command: teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14 What did I wrong? Thank you in advance! Hmm, hashing looks fine, it would rather be something in the rpc communication with Monero Ocean, although we haven't gotten any other reports for this pool. We're working on fixing some small rpc bugs, we'll make sure to test against Monero Ocean as well. I've get the same error with monero.miningpoolhub.com and wownero.ingest.cryptoknight.cc also. I've enabled the miner sw in the windows firewall rules also, so it shouldn't be a FW issue. Will take a look at both today!
|
|
|
|
peterboy1
Newbie
Offline
Activity: 168
Merit: 0
|
|
November 06, 2018, 04:27:25 PM Last edit: November 06, 2018, 04:55:05 PM by peterboy1 |
|
btw, sometimes, random of my rx570 is hashing below 1kh/s be it at start or at the middle of mining.
my temporary fix is just disabling and enabling my lan til it hashes back to its max.
hope you can reproduce it. it mostly happen on a rig with a different brand of cards.
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 06, 2018, 08:14:42 PM |
|
This is my starting command: teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14 What did I wrong? Thank you in advance! Hmm, hashing looks fine, it would rather be something in the rpc communication with Monero Ocean, although we haven't gotten any other reports for this pool. We're working on fixing some small rpc bugs, we'll make sure to test against Monero Ocean as well. I've get the same error with monero.miningpoolhub.com and wownero.ingest.cryptoknight.cc also. I've enabled the miner sw in the windows firewall rules also, so it shouldn't be a FW issue. I've tried running the latest public release (0.3.6) against all three pools now, I don't have any problems mining at gulf.moneroocean.stream:10128, us-east.cryptonight-hub.miningpoolhub.com:20580, wownero.ingest.cryptoknight.cc:50901. With the same error on all three pools, I'm guessing the issue is something specific about your setup. Have you found any pool that works? Are other CN miners working fine against the pools above on your machine?
|
|
|
|
tvukoman
Jr. Member
Offline
Activity: 69
Merit: 5
|
|
November 06, 2018, 08:34:39 PM |
|
these guys with rx 570/580 hashing below 1kh/s i think are doing it wrong. check your straps and oc.
all of my rx 570 hashes above atleast 1kh be it 4gb or 8gb. the only problem i have is micron, which i think is the worst in cn variants.
Agree, matches what we found as well. Haven't really found any card stuck below 1kh/s, except for Micron mem where we've been stuck around 860 h/s on some cards whatever we try for straps and clocks. Samsung by far the easiest, Hynix often also just a copy of lower-to-higher straps. And, I'm really not that good with straps, I should add. Great job TeamRed! Read every post here, testing rig for about 8 hours without crash. Now trying to fine tune. Here is mixed rig (1 x rx570 4GB Elpida, 2 x Vega 56 referent + 1 Vega 64 Asus Strix) Vega 56 hashing about 2000 H/s, Vega 64 2240 H/s). Vega 56 have low clock and memory 1408/1088 because on SRB is overheating and crashing on more clocks. Vega 64 is on 1520/1100. Funny thing about RX570 is that hashrate of RX570 somehow depends of configuration on Vega cards. When i first start miner (without --cn_config) RX570 Nitro + (Elpida) hash 920 H/s with timings 1200/1980. Than I experiment and put on RX570 7+7 (default was 8+7) and lower clock and memory to 1225/1940 (as user Dragonmike recommended). Playing with OverdriveNtool when hashing, been able to get 942 H/s with 1200/1920 but i think that time i put Vega 56 to 15+15. When i restarted rig, RX 570 hash just 880 H/s? Try appy OverdriveNtool with same clocks as before 1200/1920 but still 880 H/s. Than i apply 1250/1980 and still 880 H/s. mV for clock and memory 900 mV. What am i missing and is it possible and where to delete kernel files to make automatic initialization of the cards again? That sounds a little weird. I don’t know if you restarted the miner or rebooted the rig in between runs? One issue we have (which I’m a little ashamed of tbh) is our unclean shutdown. It has led to me losing perf between restarts at times. Can you reproduce your test, i.e. whenever you run the 570 only after a clean reboot you hit ~940 h/s, but 570+Vegas after a clean reboot and it’s lower for the 570? Yes, something with RX570 4GB is weird. Tested a little, two times rebooted the whole rig and whatever clocks applied max hash is just 880 H/s. Than rebooted third time, and my Task Scheduler automatic run SRB Miner.bat and apply Overdrive profile and my RX570 hash 910 H/s in V8 which is normal to me in SRB Miner for this card. And than weird again :-) start TRM and RX570 hash with same 910 H/s like in SRB :-) Bump from 880 to 910.I leave it that way from last night almost 24 hours stable running: [2018-11-06 21:28:13] Stats GPU 0 - cnv8: 910.2 h/s, avg 906.8 h/s, pool 924.0 h/s 386/0 [2018-11-06 21:28:13] Stats GPU 1 - cnv8: 1.998kh/s, avg 1.996kh/s, pool 1.895kh/s 787/0 [2018-11-06 21:28:13] Stats GPU 2 - cnv8: 2.202kh/s, avg 2.242kh/s, pool 2.232kh/s 926/0 [2018-11-06 21:28:13] Stats GPU 3 - cnv8: 1.997kh/s, avg 2.002kh/s, pool 2.002kh/s 833/0 [2018-11-06 21:28:13] Stats Total - cnv8: 7.107kh/s, avg 7.148kh/s, pool 7.053kh/s Here is this (for me) stable Setup of mixed rig with 730W from the wall (-50W and + 300 H/s): Win 10, Adrenalin 18.6.1 GPU 0 (RX 570 4GB Elpida Nitro+) 7+7 core 1180/850 mV memory: 1980/900 mV. One click strap. GPU 1 (Vega 56 ref. with 64 bios ) 16+14 core 1408/950 mV memory: 1070/950 mV GPU 2 (Vega 64 Asus Strix) 16+14 core 1520/920 mV memory: 1100/910 mV GPU 3 (Vega 56 ref. with 64 bios ) 16+14 core 1408/955 mV memory: 1088/945 mV As you can see, Vega 56 ref with Samsung mem can in your rig hash much better with more clock on core and mem, i must lower it because rig is in small space and overheating. Waiting for the winter to come :-) I tested intensity and found that Vega 56 Reference even on this lower clocks still more like 16+14, than 15+15.
|
|
|
|
Germini
Newbie
Offline
Activity: 20
Merit: 1
|
|
November 07, 2018, 06:08:34 AM |
|
[2018-11-07 03:02:09] Pool xmr-us-east1.nanopool.org share accepted. (GPU4) (4726/4575/95) [2018-11-07 03:02:13] Pool xmr-us-east1.nanopool.org share accepted. (GPU1) (4728/4576/95) [2018-11-07 03:02:13] Pool xmr-us-east1.nanopool.org failed to parse server rpc: {"id":101,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
how to fix that? what method are you guys using to have a fixed core clock ? i set it up for let's say 1400mhz for vega56 using overdriventool but when watching it with HWiNFO is not the same it's about 1350Mhz The readme file states that core clock is the way to get a better hashrate using this miner I want to take advantage of that and it is said that used ppt mod i guess that means SoftPowerTables ? any hint appreciated
|
|
|
|
|