Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: andrewbadr on September 14, 2011, 11:48:23 PM



Title: Client pegs my CPU
Post by: andrewbadr on September 14, 2011, 11:48:23 PM
The official Bitcoin client always pegs my CPU to 100% when it's running. This makes everything run slowly. Other people don't seem to have this problem. Any ideas?

Running OSX 10.6.8, client version 0.3.24-beta


Title: Re: Client pegs my CPU
Post by: Raptorblaze on September 15, 2011, 01:09:09 AM
You could change the config file so it doesn't automatically start generating coins every time you start...CPU mining is virtually pointless now anyway


Title: Re: Client pegs my CPU
Post by: andrewbadr on September 15, 2011, 02:12:14 AM
You could change the config file so it doesn't automatically start generating coins every time you start...CPU mining is virtually pointless now anyway


I'm pretty sure I have that option turned off. Wasn't it removed from the client anyway?


Title: Re: Client pegs my CPU
Post by: Revalin on September 15, 2011, 02:14:23 AM
It's removed from the settings dialog but you can still enable it in the config file or command line.

What block number does it report in the lower right?  It's normal for it to use a lot of CPU and IO until it's finished downloading and verifying the block chain.


Title: Re: Client pegs my CPU
Post by: andrewbadr on September 15, 2011, 02:35:56 AM
What block number does it report in the lower right?  It's normal for it to use a lot of CPU and IO until it's finished downloading and verifying the block chain.

Yes, it's catching up on the block chain. If using 100% of the CPU is intentional, I guess it's just bad design.


Title: Re: Client pegs my CPU
Post by: Revalin on September 15, 2011, 02:38:46 AM
Verifying history just takes a lot of CPU.  The fix people are discussing is to download some pre-verified chunks to seed it to 98% and then just process the last 2%, but that's not ready yet.


Title: Re: Client pegs my CPU
Post by: andrewbadr on September 15, 2011, 02:42:37 AM
Verifying history just takes a lot of CPU.  The fix people are discussing is to download some pre-verified chunks to seed it to 98% and then just process the last 2%, but that's not ready yet.

Another fix would be to use at most, say, 50% of CPU. I'm sure most users would prefer that to the current operation, and it's a simpler change than downloading pre-verified chunks.


Title: Re: Client pegs my CPU
Post by: ohforf on September 15, 2011, 04:23:53 AM
Is it possible to reduce Task/Process/Thread Priority in OSX ?
Every half decent OS has Ways to do that, so there is hope.  ;D

By the way, whats your Hardware ? A faster CPU with more Cores might help a little...