Quote from: Oschoir on May 29, 2018, 03:59:34 PM

At what point in the mining cycle do new mempool transactions typically get added to the Merkle tree of a candidate block and what variables govern this?

Is a mempool snapshot taken once and then mined until a winner arrives or is found?
Or does cgminer continually add new transactions to the existing block opportunistically? If so is there any impact on the hashing speed due to the re-computation of the header? Maybe there isn't since the CPU can do that, while the ASIC does the mining? I suppose that would be an opportunity to reset the Nonce too.

Thanks for any insights, I am not a miner, but interested in the effect on the mempool and chances of a new TX getting into the next block.

The mempool snapshot is done at the server level in the bitcoin daemon which is handed off to the mining pool, about once per minute so they're always up to date. Cgminer is at the client end and does not do any of this unless you are solo mining with it.