One of my S3's overclocks like a beast!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
That is a lot of discarded shares, how does that work out?The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
Does anyone know how to change the command line arguments ran from cron for cgminer on antminer s3? I want to add scan-time and lower the queue, I'm getting way too many discarded it does not look good. Hashrate is steady and HW is low, but the discarded work on one of the miners is ridiculous
54m 56s
420.61 5s
429.34 avg
1,308 accepted
1 rejected
31 hw
1,233 discarded
PM Me. I've been trying to find someone to discuss this with for a few hours now. Default queue setting on the S3 is 4096, which just seems insane. I've been playing with adding scantime and expiry with little result. I have not touched the queue yet. I'm waiting to see if anyone knows my BMT set it so high to begin with.
it is my understanding it is a cronjob running cgminer with launch options ?