Avalon 200 clone hash rate discrepancies

mehdi343

newbie

Activity: 29

Merit: 0

Quote from: stephenm on February 11, 2014, 11:12:28 PM

in case anyone is interested, I fixed the problem by using a stratum proxy

220 GH/s locally and on pool side

Would you please tell me how did you fix it? I have the same problem. Anybody knows how to fix with proxy?

mehdi343

newbie

Activity: 29

Merit: 0

How did you fix it by proxy? can you explain more?

stephenm

newbie

Activity: 37

Merit: 0

in case anyone is interested, I fixed the problem by using a stratum proxy

220 GH/s locally and on pool side

stephenm

newbie

Activity: 37

Merit: 0

upping this one last time in case some had an idea?

no matter stock or o/c'ed to 1400 it's hashing with a ratio (DiffS / Local Work) of 12-15% no matter either pool (only tried BTCguild and BTCdig).
API log shows very consistent numbers throughout the 16 miners (all within 1% of each other).

Local hashing rate (Cgminer status page) is on spec (200 stock) - (215/220 @ 1400).

stephenm

newbie

Activity: 37

Merit: 0

odd - cgminer status now says the btcguild server is dead.
I thought it was another problem with this unit but I just added the btcdig info again and it's connecting/hashing fine with btcdig.
my other miner on btcguild is still working fine though. like I said - odd.

stephenm

newbie

Activity: 37

Merit: 0

Are these numbers what gives an idea of the number of errors?

(17 hours 35 mn)
LocalWork: 2,870,281
DiffA: 2,050,944
DiffR: 29,824
DiffS: 729,728

stephenm

newbie

Activity: 37

Merit: 0

thanks for the input guys.
bought it directly from the manufacturer in China.
I'll contact them to have it replaced/fixed/whatever.

there is definitely something I tried all my other miners on the same pool and not a single one of them is more than 1-2% off the hashing speed spec.

my temperatures are a little higher than what some of you have been running but I don't see how this could explain it. heck, they even recommend a target temp of 50C.

samsonn25

hero member

Activity: 882

Merit: 1003

Thats alot of stale shares!

I have 4 ants mining now, 14 hours 9000-14000 shares each and not even 1 stale.

marcbuster

newbie

Activity: 2

Merit: 0

Where did you get the clone? Just curious... Tongue

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

I'm pretty sure its because of the amount of stale and discarded shares, which are due to hardware errors. You also have a high amount of get fails at 10%. These figures are massively higher than I get.

I'm at a bit of a loss here to be honest, maybe someone else can chip in. The only thing I can see that looks like it could be causing it is that your temp is a little on the high side, these really need to be kept cool, where have you got the miner?

We keep ours in an unheated cargo loading area and they never get over around 42 degrees.

stephenm

newbie

Activity: 37

Merit: 0

here's the cgminer status page after 45 mn

http://postimg.org/image/jvn5wqka5/full/

where do I see the number of errors? and %?

still averaging ~ 140 GH on the btcguild stats..

stephenm

newbie

Activity: 37

Merit: 0

well that didn't fix it Sad

averaging 140-150 GH on the pool's stats, and 195-205 on the cgminer status page.

could it be related to not enough internet bandwidth? my connection isn't great and I actually have no clue how much bandwidth a total of 330GH miners would need.

stephenm

newbie

Activity: 37

Merit: 0

thanks, changing to 128, I'll update in 30 mn or so
thanks for the support!

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

128

stephenm

newbie

Activity: 37

Merit: 0

oh I misunderstood
the other miner is just a block erupter cube that I still have

what difficulty should I have the worker? 128 or 256?

I set it to 256 for now..

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

On your first shot of btc guild there are 2 workers. What machine is the 2nd worker from? They are not both on the avalon are they?

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

When I said new worker I meant on btc guild.

Try creating a new worker on btc guild and then enter only that worker on pool 1. Leave pool 2 and 3 blank

stephenm

newbie

Activity: 37

Merit: 0

yes this is a brand new unit
config:
http://postimg.org/image/dz8ipj2gz/full/

and here's the chart:
http://postimg.org/image/cbo27aae1/

(it has only been working for a day or so)

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

was it a brand new worker. Please post the CGminer config page.

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

show the guild stats graph page

stephenm

newbie

Activity: 37

Merit: 0

well, things are worse now
here's what the Cgminer status page shows.
I also copied/pasted a screenshot of the pool stats (which I reset at the same time as I restarted the miner @ 1300)

http://postimg.org/image/4qq8phuy1/full/

stephenm

newbie

Activity: 37

Merit: 0

Thanks - We'll see how it goes at 1300. But that's how I first set it up and I already had that big 20+% discrepancy.

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

Quote from: stephenm on January 30, 2014, 03:48:21 PM

thanks I am doing this right now, I'll refresh the stats on btcguild too.

edit: what about pool balance? what should I have there?

Failover

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

I can see from your 3 hour mhash average you have been overclocking too much. That is your problem.

stephenm

newbie

Activity: 37

Merit: 0

thanks I am doing this right now, I'll refresh the stats on btcguild too.

edit: what about pool balance? what should I have there?

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

and look at your discarded and rejected figures, lots of error there. The problem is it will be giving you an aaverage hash speed of your workers so the previous error ones when you were running at 1500 will be added in.

Start on BTCGuild at 1300. Run for 30 mins and post another screen shot of the miner and your BTC guild stats page.

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

too fast, you'll kill it at that speed without a 1250 power supply and temp 2 is way too high, you want to keep it under 45 really

stephenm

newbie

Activity: 37

Merit: 0

Thanks for taking the time to respond, here's screenshot from yesterday:
http://postimg.org/image/tgy1lcntb/full/

Since then, I upgraded to the newer firmware (end december) and I get similar results.
I tried running at 1300 and 1400 (and 1500) and I still get about 25% lower hashing speed on the pools' stats.

thanks!

studio1one

hero member

Activity: 1218

Merit: 500

BintexFutures

Quote from: stephenm on January 29, 2014, 11:43:29 AM

Hi
I've been mining on the btcdig pool for some time using some block erupter blades with no problem; i.e. hash rate reported by the pool for each miner is spot on.
I just installed a avalon 200GH/s clone (with the openwrt interface) and while it is apparently hashing on spec at 200GH/s (I even tried overcloking it to 230GH/s with apparently no problem), the pool is reporting a hash rate of only 150-160GH/s.

I tried adjusting the difficulty which didn't change anything - I waited several hours in between each change to make sure I was reading a correct figure.

I am not sure what I am missing here, could it be a limitation by the pool?

Any help is appreciated, thanks!

-S.

post a screen of your CGMiner hashing page on the box please.

Chances are that it is because of the amount of errors. Are you overclocking? this can be counterproductive as it produces more errors than the speed gain gives.

Also what are your temps. These Avalon chips like to run cool, the hotter they are the more errors there will be.

It is normal for a pool to show a lower hashrate than a box but that seems excesssive.

stephenm

newbie

Activity: 37

Merit: 0

Hi
I've been mining on the btcdig pool for some time using some block erupter blades with no problem; i.e. hash rate reported by the pool for each miner is spot on.
I just installed a avalon 200GH/s clone (with the openwrt interface) and while it is apparently hashing on spec at 200GH/s (I even tried overcloking it to 230GH/s with apparently no problem), the pool is reporting a hash rate of only 150-160GH/s.

I tried adjusting the difficulty which didn't change anything - I waited several hours in between each change to make sure I was reading a correct figure.

I am not sure what I am missing here, could it be a limitation by the pool?

Any help is appreciated, thanks!

-S.

Topic: Avalon 200 clone hash rate discrepancies (Read 2067 times)