• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can client overload CPU?

shulgin78

Member
I've only recently downloaded the Distributed.net client and regularly leave it running overnight, could this overheat my CPU (being at 99%+ for long periods)?
Also since installed I also recieve the OGR packets, can I just work the RC5 pkts?
Finally I've just read that my AMD K6-2 should ONLY have 3 pkts in the buffer at one time, yet I usually get 12 pkts with no apparent problem, so why the warning?
 
1. No unless you already have a problem with your CPU's cooling.

2. If you want to do RC5 you should set it at the clent's config. At the buffer's options go to - Load-work precedence and enter:

RC5,DES=0,CSC=0,OGR=0

3. I have 3K blocks in my in-buffer which is more than 100 packets with the packet size set to 32 blocks. Where did you see this warning?
 
If your cpu has adequate cooling there should be no problem.

To not do OGR edit your ini file to include a misc section and in it type:
project-priority=RC5,DES=0,CSC=0,OGR=0

The 3 packet limit is an OGR thing,if you are doing RC5 set thr fetch to whatever seems right to you.

THE source for setting up and running Dnet clients:

Here
 
The client actually does use 99%+ of the otherwise-wasted CPU cycles, but it doesn't necessarily use all the transistors in the CPU. I remember when Distributed.net was running the short-term CSC project late last year, and we found that CSC was making our processors run considerably hotter, perhaps 3C to 6C hotter, presumably because it did use a lot of transistors, including the MMX units.

Welcome to Team Anandtech! : )
 
Back
Top