Reckman (OP)
|
|
January 09, 2014, 07:45:38 PM Last edit: January 10, 2014, 02:10:15 AM by Reckman |
|
Has anyone seent this? I know there is variance and estimated hash rates at the pool. But the discrepancy is huge. Is there something with my CGminer config? CPU and Ram are well below capacity. CGminer is stable. Thanks for your help. , "intensity" : "19,19,19,19", "vectors" : "1,1,1,1", "worksize" : "256,256,256,256", "kernel" : "scrypt,scrypt,scrypt,scrypt", "lookup-gap" : "0,0,0,0", "thread-concurrency" : "8192,8192,8192,8192", "shaders" : "1280,1280,1280,1280", "gpu-engine" : "1050,1050,1050,1050", "gpu-fan" : "0-85,0-85,0-85,0-85", "gpu-memclock" : "1500,1500,1500,1500", "gpu-memdiff" : "0,0,0,0", "gpu-powertune" : "20,20,20,20", "gpu-vddc" : "0.000,0.000,0.000,0.000", "temp-cutoff" : "95,95,95,95", "temp-overheat" : "87,87,87,87", "temp-target" : "85,85,85,85", "api-mcast-port" : "4028", "api-port" : "4033", "api-listen" : true, "api-network" : true, "api-allow" : "W:127.0.0.1", "expiry" : "120", "gpu-dyninterval" : "7", "gpu-platform" : "0", "gpu-threads" : "1", "hotplug" : "5", "log" : "5", "no-pool-disable" : true, "queue" : "1", "scan-time" : "30", "scrypt" : true, "temp-hysteresis" : "3", "shares" : "0", "kernel-path" : "/usr/local/bin" }
|
|
|
|
Reckman (OP)
|
|
January 09, 2014, 10:30:36 PM |
|
o.O
|
|
|
|
cryptomining
|
|
January 09, 2014, 11:28:05 PM |
|
thats not variance, you got problems for sure, you should have 0 hardware errors and at least double wu. what gpu's?
|
|
|
|
Reckman (OP)
|
|
January 09, 2014, 11:58:06 PM |
|
thats not variance, you got problems for sure, you should have 0 hardware errors and at least double wu. what gpu's?
r9 270 gigabyte models why does cgminer show 1.8 mhash? thats what these cards should get
|
|
|
|
mrmork666
Member
Offline
Activity: 98
Merit: 10
|
|
January 10, 2014, 12:04:30 AM |
|
first try reducing -I 18 on all of the cards and see if that has difference on the hardware errors you are getting (hw)
|
Join The Zeitcoin Movement Zeit : MhcEMb6YvZCnb4TPnti74p4s6mNiRvGMbQ | Ltc : LVAfAYf3dr47v5JbVRbGHfqUfKPLTx9Vnk
|
|
|
Reckman (OP)
|
|
January 10, 2014, 12:18:22 AM |
|
Thanks for helping guys, I will tip for solution and help
|
|
|
|
Reckman (OP)
|
|
January 10, 2014, 02:01:53 AM |
|
hmm this is bizarre I've never had anything like this
|
|
|
|
cozk
|
|
January 10, 2014, 02:21:27 AM |
|
Try another pool.
The pool is estimating your hashrate.
Imho there is an issue on their side.
Cgminer is 100% accurate on your hashrate, pools are estimating it based on the shares you submit.
Change pool and it should be fixed.
|
|
|
|
Reckman (OP)
|
|
January 10, 2014, 02:24:25 AM |
|
I have tried another pool,
look at the WU variance, the hash rate shouldn't be the same with WU of 50% more.
|
|
|
|
_destro
Newbie
Offline
Activity: 11
Merit: 0
|
|
January 10, 2014, 03:58:26 AM |
|
Well, generally, HW errors means that the card is being pushed too much in some way. Lowering the intensity seemed to help a bit, but I'm suspecting the memory clock might be a little too high. Some of these R9s can be pushed quite a bit on the memory/core clocks, and some can't. I have a few R9 290s that are rock solid at 1500, and 2 others that don't like anything above stock.
Try this:
"gpu-memclock" : "1350"
If that seems to clear up the HW errors, and the WU is pretty close to the reported hashrate, I'd toy with bringing intensity back up to 19. I'd also try to slowly increase the thread concurrency. Many of these R9 270s can get up to 16000 TC.
|
|
|
|
Reckman (OP)
|
|
January 10, 2014, 04:21:35 AM |
|
Tried, running stock still having this issue, hmm wonder whats causing this o.O
|
|
|
|
Reckman (OP)
|
|
January 10, 2014, 04:41:54 AM |
|
|
|
|
|
_destro
Newbie
Offline
Activity: 11
Merit: 0
|
|
January 10, 2014, 04:50:22 AM |
|
Oh, how about this:
Set lookup-gap to 2.
|
|
|
|
ymer
|
|
January 10, 2014, 05:58:47 AM |
|
I'm pretty sure it's the pool, make a quick try on a different one.
|
|
|
|
maardein
|
|
January 10, 2014, 09:06:53 AM |
|
I think your thread concurrency might be the problem. First, you don't need to set shaders and thread concurrency (tcc), since cgminer will automatically determine tcc when you set shaders. So, I would delete the tcc line, and keep the shader line.
Also lookup gap at 2, like suggested before, could be a good start.
|
BTC: 1788UegKXGXXicfPcbZ1bmSUJ99ZWRCF7p LTC: LZ2rCcoxK4X8wRRynqdxoimd4d3TDNk7Lk PMP: PApSSdorQds5tQysymwDXPAN3viJLFTUs8
|
|
|
bmoconno
Sr. Member
Offline
Activity: 280
Merit: 261
New In Town...
|
|
January 12, 2014, 01:17:06 AM |
|
The discrepancy you're seeing in cgminer's reported hashrate and the hashrate reported by the pool is a direct result of the HW (Hardware Errors) that your cards are producing. The number of HW should always be zero when scrypt mining. I'd bet dollars to doughnuts that all those hardware errors are the result of running Powertune @ 20 on all four cards. Here's how I would resolve this problem: (NOTE: IGNORE YOUR HASHRATE WHILE WE TRY TO REMOVE HW ERRORS) - At the command prompt enter the following commands:
- setx GPU_MAX_ALLOC_PERCENT 100
- setx GPU_USE_SYNC_OBJECTS 1
- Edit your .conf file:
- Change "gpu-powertune" : "20,20,20,20", to "gpu-powertune" : "0,0,0,0",
- Remove the "shaders" : "1280,1280,1280,1280", line entirely.
- Change "gpu-engine" : "1050,1050,1050,1050", to "gpu-engine" : "900-1050,900-1050,900-1050,900-1050",
- Add this line: "auto-gpu" : true,
- Delete any .bin files in your cgminer directory.
- Restart your machine, then run cgminer with your newly edited .conf file
If cgminer is now running without HW errors, I would recommend (as others have suggested) increasing your thread-concurrency to 16000. If you previously had problems doing this, the variable commands (setx) I had you enter should have resolved that. From there, I would either slowly iterate values for settings (gpu-engine/powertune) until you get your hashrate at an acceptable level with zero HW errors.
|
If I've helped you out, or you just think I'm awesome… 13SZex4uANVrfTeeuFEXGu6W8EVYtWVB53
|
|
|
damiano
Legendary
Offline
Activity: 1246
Merit: 1000
103 days, 21 hours and 10 minutes.
|
|
January 12, 2014, 02:03:13 AM |
|
Im using a R9 270x as a backup atm and your config is way to aggressive.
I do about 390-414k
I 15
powertune 0 then 10
try it out
|
|
|
|
mikeyfinn
|
|
January 12, 2014, 02:31:26 AM |
|
Did you say a gigabyte 270x? if so, try this for options: -I 19 -g 1 -w 512 --lookup-gap 2 --thread-concurrency 15232 --gpu-engine 1130 --gpu-memclock 1500 --gpu-fan 85 this is what i use and i get ~480 with no HW errors
|
Bitcoin: 1KZr3AvQ3m8NWEGbBPzFMFXbzHxpCbkbv4 Huntercoin: HQWSihm1WPJfjdPbeLfdVc6nsqrnJW5fYR Sync: Si1MjELBXaffuNgEN4Zd3PkM9qzu9pq5k5
|
|
|
Reckman (OP)
|
|
January 12, 2014, 02:34:36 AM |
|
they are regular 270 cards not 270x running stock still gives some errors and shitty WU "intensity" : "13,13,13,13", "vectors" : "1,1,1,1", "worksize" : "256,256,256,256", "kernel" : "scrypt,scrypt,scrypt,scrypt", "lookup-gap" : "2,2,2,2", "thread-concurrency" : "4032,4032,4032,4032", "shaders" : "0,0,0,0", "gpu-engine" : "0-0,0-0,0-0,0-0", "gpu-fan" : "0-85,0-85,0-85,0-85", "gpu-memclock" : "0,0,0,0", "gpu-memdiff" : "0,0,0,0", "gpu-powertune" : "0,0,0,0", "gpu-vddc" : "0.000,0.000,0.000,0.000", "temp-cutoff" : "95,95,95,95", "temp-overheat" : "85,85,85,85", "temp-target" : "75,75,75,75", "api-mcast-port" : "4028", "api-port" : "4028", "expiry" : "120", "gpu-dyninterval" : "7", "gpu-platform" : "0", "gpu-threads" : "2", "hotplug" : "5", "log" : "5", "no-pool-disable" : true, "queue" : "1", "scan-time" : "30", "scrypt" : true, "temp-hysteresis" : "3", "shares" : "0", "kernel-path" : "/usr/local/bin" }
|
|
|
|
Reckman (OP)
|
|
January 12, 2014, 02:50:04 AM |
|
|
|
|
|
|