WorkDelay is the new option I added to fix the massive waste of CPU by their driver ...
MinerCount and AsicCount match the hardware so you don't change them.
Thank you, I could figure out the first ones you listed, but these were some I was wondering about.
I figured the two counter were tied to hardware, but what do they mean?
Should WorkDelay ever read anything beside 1; is it a 0/1 toggle?
What is an example of BadWork?
Work delay is only settable by editing /etc/init.d/cgminer - but for the S3, 1 is optimal and it's the default inside cgminer.
I spent days/weeks adjusting it from 1 to 3 and ended up deciding 1 was best
1ms delay means it checks to send work about 1000 times a second (instead of about 60,000 times - wasting much CPU)
The two counters - well - ask bitmain they put them in the --bitmain-options
The first one is how many sets of data are returned ... so that's why the table above it has 2 rows.
It's somewhat like saying it has two cards (as the S3 does)
BadWork is a new cgminer API value - it counts work from the pool that has very few transactions - i.e. bad for bitcoin.
Some pools send one of them every network block change ...