I would like to share my deep doubts about the sense of changing cgminer queue parameter.
I know there are many guys here setting queue to 0, but documentation says there has to be 0+ (nonzero) value, so if You set 0 You set 1.
Bitmain sets default 4096 for S3, 8192 for S4/5 units. Personally I do not see ANY difference in what is set there. Yes, ckolivas has written few times, that probably that number is too high, but he also says, he is not author of a driver. So we have to suppose it is better to set there 1 just because it is default setting of cgminer?
Spondoolies... I do not have any idea what queue value is it using, but probably default, so probably 1. I did not study it too much, but are there the same chips? Probably not.
I know there are many guys here setting queue to 0, but documentation says there has to be 0+ (nonzero) value, so if You set 0 You set 1.
Bitmain sets default 4096 for S3, 8192 for S4/5 units. Personally I do not see ANY difference in what is set there. Yes, ckolivas has written few times, that probably that number is too high, but he also says, he is not author of a driver. So we have to suppose it is better to set there 1 just because it is default setting of cgminer?
Spondoolies... I do not have any idea what queue value is it using, but probably default, so probably 1. I did not study it too much, but are there the same chips? Probably not.
Deep doubts? I posted the results of queue 0 v queue 1 a while ago here:
https://bitcointalk.org/index.php?topic=18313.msg8348972#msg8348972
It is not a hard & fast rule, as everyone has a different set up & different circumstances - so it's best to try both for a while & check the results. Also, I've only ever found that changing the queue setting to 0 only benefits Bitmain hardware, probably due to the inferior firmware/hardware, as my Spondoolies gear runs fine with the default cgminer queue setting of 1.
It's a case of testing, checking & testing again.....
IYFTech so will this fix my p2pool issue as you can see in my images below my S1 works fine and finds share with a BS around 5 million but my S3 has never worked right highest best share in a week was 8 million.
Antminer S1
http://i.imgur.com/hXv9p9g.png
Antminer S3
http://i.imgur.com/k8AHDDh.png
Someone told me it was a "luck" thing but I don't think so having same issues with it on regular pool mining also...
Thank You. It seems clear. Can You please share which firmware/cgminer versions are You using there?
Yeah sure, the test was done using the August 26th firmware (antMiner_S320140826.bin) with ckolivas S3 binary that fixes the stale share submission issue that Bitmain ignored. I found this firmware to be the most stable version for my S3's, & when used with ckolivas's binary they finally performed as they should do with p2pool
NVRmind I found link but how is it installed what just SSH in and exchange the cgminer in the S3 for this one?