Re: Pool mining and miner requesting new work, although it still should have some
Ah okay. Thank you very much for clearing things up for me. I think i have a better understanding of what's going on, now. But i think there is an additional reason, why the client fetches new data. This is because my CPU miner, which is ofc. very slow, requests new work every somewhat 60 seconds and i doubt, that it can go through all nonces in this short time.
Another thing i've noticed btw.:
My version of proclbm (included with guiminer) is not updating it's internal timer, when getting new data through a long poll. It will fetch new work every X seconds, no matter if it got new work through a long poll a second ago. I didn't notice this behaviour in DiabloMiner, so i think it's not meant to be this way.
This supports my theory, that there has to be another or additional reason for the client to fetch new work, me thinks.
But, in the end, a lot of getworks are not bad for me, but for the pools, because they get more requests, right? I don't think i should have to care about that too much any further, should I?
Another thing i've noticed btw.:
My version of proclbm (included with guiminer) is not updating it's internal timer, when getting new data through a long poll. It will fetch new work every X seconds, no matter if it got new work through a long poll a second ago. I didn't notice this behaviour in DiabloMiner, so i think it's not meant to be this way.
This supports my theory, that there has to be another or additional reason for the client to fetch new work, me thinks.
But, in the end, a lot of getworks are not bad for me, but for the pools, because they get more requests, right? I don't think i should have to care about that too much any further, should I?