Re: CGMINER GPU FPGA overclock monitor fanspeed RPC linux/windows/osx/mip/r-pi 2.7.0
...
Sort of related, I had a different question - is it possible for you guys to do the opposite of how you will grab long poll from a different pool that you have set up if the primary pool does not support it, so that you could add a local bitcoin client to check for blocks that could possibly find a new one before long poll does?
There's no way I'd be the first to think of this, so I just assumed it's not doable, or perhaps not worth doing? Just curious I guess.
edit: typo
Bitcoind doesn't have LP in it.Sort of related, I had a different question - is it possible for you guys to do the opposite of how you will grab long poll from a different pool that you have set up if the primary pool does not support it, so that you could add a local bitcoin client to check for blocks that could possibly find a new one before long poll does?
There's no way I'd be the first to think of this, so I just assumed it's not doable, or perhaps not worth doing? Just curious I guess.
edit: typo
It does have an option to run a command on a block change that you can configure yourself.
I have thought of this before with the API - being able to send a message to the API when a block change occurs, however there is one more thing in an LP that would be missing:
The LP includes work on the new block.
Without this work, the LP is simply telling cgminer to go and do a request for work and thus there is the network delay of waiting for work from the pool.
I will skip certain specific details, to protect the innocent
, but this process would probably be worse than waiting for the LP... except when LP's are slow ... which has been happening more frequently in the last few months ... but only if the pool would actually return work during it's LP phase (which wouldn't make much sense since it will already be trying to send you work)
However, this could also lead to stalling the miner due to requesting work from the pool and waiting for it, but then simply getting a piece of work for the same 'previous' block if the pool doesn't already know about the new block.
LP design sux and always has since Deepbit came up with the idea (as I have mentioned before as well) - it needs to be faster (e.g. a simple UDP packet TO the miner might perform a lot better)