i made a previous post about my fan going crazy but that was me not communicating very well as that was what i was hearing and in fact looking at the cpu usage it was jumping around. I have the same problem on malaria control, so im on world community grid right now, was on docking.

i made a previous post about my fan going crazy but that was me not communicating very well as that was what i was hearing and in fact looking at the cpu usage it was jumping around. I have the same problem on malaria control, so im on world community grid right now, was on docking.

Have you set BOINC to use a certain percentage of your CPU time?

You might already know this stuff, but in case you don't, and the above is correct then on the latest version of BOINC that setting is under Tools > Computing Preferences > Processor Usage > Use at most X CPU time.

If that's less than 100% then BOINC will make the project application take a break from crunching for that percentage of every second (I think it works on the basis of 1 second anyway).

---

yes i am aware of the 100 percent usage setting issue and took that into consideration, i still have the same problem.

I believe BOINC achieves the CPU % desired across a 10 second interval. This still provides the desired control on heat levels, without imposing excessive overhead on the computations being done.

So if you tell BOINC to run with 70% of CPU, it will allow tasks to run for seven seconds, and then not allow them to run for 3. I word it that way because these tasks are still marked to run at low priority. So if higher priority work is ready for CPU during the 7 seconds, the tasks may not get 7 seconds, they might only get 4. The 3 second suspension from running though would always be 3 seconds.

---

Rosetta Moderator: Mod.Sense