4.3 Readcount Timeout
After we send one command packet to the chained chips, that BIG chip will cover all the 32 bits nonce in a certain TIME. So we must send a new work to it before that, otherwise its hash power is wasted.
Cgminer’s readcount timeout is used for that. Every count means 0.1 second. We now set the readcount to be 3/8 of the covering time. It may be 3/4 later.
I'm not a coder at all but like to look through the driver file to get a vague idea of what is going on. very vague idea
Anyway, it looks to me they chose 3/4 in the current driver. I'm still not sure of the affect. Just guessing here but I think we'll see reduced errors as the dev's pick apart and improve the code. There are a lot of variables to balance: the number of chips, the difficulty of the work, the timing to send work to the pool so it is not stale and the timing of getting new work to the chips so they're not idle.
The current software is one size fits all, 6 chips or 96 chips, same software. We might need a spinoff branch just for the 6 chip miner. It would be great if we could get per chip tuning for the 6 chip miners.
