Antminer S3 - High Stale Shares

[Westport]

Hello All,

I just installed a batch of S3 Ant Miners and am seeing a high reject rate from what I think is due to stale shares.
I could imagine several things I might need to look into to resolve.  Can someone recommend the best course of action to take?

See screen shots of below.  Any advice would be appreciated.
http://digserum.com/jing/2014-08-13_1104.png
http://digserum.com/jing/2014-08-13_1042.png

Westport

[1713956269]

1713956269

[1713956269]

1713956269

[1713956269]

1713956269

[zaqco]

I'd like to know this too.  I just got my first pair of S3's and I thought everything was fine for a while, it wasn't showing any rejected.  But I looked at the chart and there seems to be a lot of STALE shares.

https://i.imgur.com/2CBgOY0.png

I've read that this isn't a power problem, but what is it?
Any help would be greatly appreciated.

[philipma1957]

your images are pretty much worthless.  you are showing poolside info.  the pools could be under ddos attacks or internet issues thus making your info look bad.

post shots of this.

my machines love freq 231.25

[zaqco]

Thanks, here are mine:

First:
https://i.imgur.com/90Cg5r4.png

Second:
https://i.imgur.com/hPaUJr3.png

[philipma1957]

Zaqco  your numbers are good on the miner side..  

so the issue is the net connection or ghash.io


I suggest you join another pool like btcguild.com  run 1 unit there and 1 at ghash.io

do it for a day note your stats.  flip the pools on the miners run for a day and note your stats.


So far with the s-3's  my best results have been using btcguild.

I have used :

bitminter.com
btcguild.com
bitsolo.net
ghash.io


by best results I mean btcguild seems to allow more of my hash to be counted then any of the other pools.


here is a pretty fast way to check if you are mining okay  take hw/diffa      so 2 wrong out of 727,000  is good as is 3  wrong out of 743,000  that is not perfect way to calc errors  but fast and close to accurate.

I noticed something my  lsdiff settings are 256 yours are 1024  that setting my be the problem

the miners do 450 or 440 so 1024 is a high setting.

[zaqco]

Alright, will do.
Thanks for the help, philipma1957.

[philipma1957]

Alright, will do.
Thanks for the help, philipma1957.

check my edit above I found  your lsdiff settings are high on ghash.io they are 1024  try 256 or 512


I find having the diff setting at the pool just under or just over the miner is good.. so a 440 miner at 256 or 512 is better then 1024

[Rabinovitch]

My own research has shown that best pool depends of internet provider in your particular case. And you should determine which pool among your lovely/desireable pools wil be an optimal one for your provider (so as backup pools should be determined in the same way).

Tentatively you can seek for a ping value 200 ms and lower (see the screenshot below, just for example):



As usual, the lower is the better.  
If the value of the ping duration satisfies this condition, try to mine on this pool and see if rejected shares quantity is OK or not. Remember that sometimes you can just push "Save&Apply" button again, and rejected shares percentage will became reasonable. If not, then just change the pool.   Anyway they all are almost the same IMHO.  

Thus I can't mine on my S2 at Eligius. Somehow I can't ping it's address at my work where S2 is placed. At the same time triplemining, slush's, itzod, ozcoin (EU server), ghash.io and BTCGuild are OK and may be used as main/backup pools...