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/
Topic: Avalon 200 clone hash rate discrepancies - page 2. (Read 2050 times)
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.
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 edit: what about pool balance? what should I have there?
I can see from your 3 hour mhash average you have been overclocking too much. That is your problem.
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?
edit: what about pool balance? what should I have there?
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.
Start on BTCGuild at 1300. Run for 30 mins and post another screen shot of the miner and your BTC guild stats page.
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
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!
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!
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.
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.
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.
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.
Jump to: