Hi.
I was fighting with this too ![Smiley :)](https://forum.biblepay.org/Smileys/default/smiley.gif)
I have ordered "weak" linux based VPS for 24/7 wallet but I wanted to run boinc there too.
So, my solution is: run biblepay with setgenerate true 1. Of course it consumes more than 90% of CPU
so rosetta won't work. But than I install "cpulimit" (apt-get install cpulimit). It is very useful for this. Than you can usse it with command like this: "cpulimit -b -l 15 -m -p 1607" what means allow PID nr 1607 to spend max 15% of CPU. After this my BBP process consumes 15-20% of CPU and rosetta eats rest to 100 ![Wink ;)](https://forum.biblepay.org/Smileys/default/wink.gif)
And shared wallet was of my thought too. What about creating some Rosetta/BBP pool? Rob will it be possible to change pool to handle this?
We dont need a pool, because the boinc infrastructure is already pooling the RAC for us.
Id rather simplify the infrastructure than make it more complicated.
Regarding the Gridcoin pool that T-mike mentioned, they have a pool because they dont have enough blocks per day to pay the researchers. We dont need a pool, because we airdrop the payment once per day.
Regarding mobile devices, we may be able to add a feature to not require PODC updates on tablets and smartphones - but thats still in the wish list - I have not looked at that yet.
Jaap, regarding one thread using too much power, I already made it sleep 200ms between iterations, it could be that you are running this on a low power machine, I suppose I can put in more granular control over this to see if this can be improved. Right now on my windows dev machine, Im running rosetta 6 tasks : taking 50% of the cpu, the plain vanilla biblepay on 1 thread is taking 13% of the cpu, and its hashing at 270hps in testnet. So of course we have to consider the fact that we *do* want it hashing on 1 thread so we have a baseline level of average security. But nevertheless, Ill add a setting to see if we can control the sleep better, and, have it actually attempt to sleep more often - there is also something that I need to look at for the miner process as far as CPU priority - it might be set to high and not normal, meaning that on certain machines its not listening to your wishes, ill check into all that today.
I think what will end up with the regular pool, is I have no intention on taking it down - I still want to make it a place for "Biblepay Central", for Reports, for Orphan related letter writing and functions, but the heat-mining pool might be removed. If we keep compatibility with the heat mining side, which I believe we have done so far, I may let it run and see what kind of interest we have and what the numbers look like, but most likely with everyone running on one thread, it wont be necessary to have a pool for heat mining and I may end up shutting that feature down.
At that point we would be fully Rosetta decentralized, with no pools.