One of the systems I have is a desktop having hyperthreading. This computer runs two copies of Boinc CPDN (only CPDN, nothing else). Once every few days it simply stops with the message that \"computer is overcommitted\". This happens despite the fact that there\'s no load on the coputer at the time and no other app runs. It also doesn\'t inform me in any way (say, a message window); what usually happens is that, a couple of days later, I find out by chance that the system hasn\'t done anything more productive than wasting electrical energy for a couple of days. You probably understand that this is just the kind of stuff that makes people angry enough to uninstall. I haven\'t unistalled yet, but I\'d really like to know what I can do to make the system run continuously.

---

Can\'t get to the database to check your machines and Runs at the moment. Must say, though, that I ran five P4s and never experienced that. It makes me wonder whether the machine is overheating; P4s self-protect with thermal throttling.

Have you opened the box and blown dust from the heatsinks and fans recently? Might be worth a look.

There are free programs on the Net that can help monitor the computer\'s internal temperatures: SpeedFan and Everest Home. ASUS motherboards also have a proprietary version on the software CD. Throttlewatch is also useful.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Hi 9 Souls,
First know that you have friends in the US who support Israel without question. I\'m unfamilar with CPDN, but standard Boinc for windows will run continously when setup, divided between the projects that are running and can be individually suspended or shut off to allow a project to run full-time. Most intel P-4 or Pent D processors will run as two processors. If standard Boinc will work, you might try it, but I don\'t know if the file will transfer. You can see in task mngr what is running, by alt-ctrl-del or type msconfig into the run button in start to configure programs that startup when windows starts.
Geojim

---

One of the systems I have is a desktop having hyperthreading. This computer runs two copies of Boinc CPDN (only CPDN, nothing else). Once every few days it simply stops with the message that \"computer is overcommitted\". This happens despite the fact that there\'s no load on the coputer at the time and no other app runs. It also doesn\'t inform me in any way (say, a message window); what usually happens is that, a couple of days later, I find out by chance that the system hasn\'t done anything more productive than wasting electrical energy for a couple of days. You probably understand that this is just the kind of stuff that makes people angry enough to uninstall. I haven\'t unistalled yet, but I\'d really like to know what I can do to make the system run continuously.

Hi,
Well, the overcommited procedure is not linked to overheating, but to the fact that BOINC estimate that there\'s not enough time to compute one WU until its deadline, this computation depends on <on_frac>(computer is on), <cpu_efficiency> (usage for boinc), <ressource_share> (share per project), <duration_correction_factor> (linked to previous results for project) of client-state.xml and of course benchmark results.
As I see your Benchmark results are really poor for a 2.60Ghz, may be you had a benchmark test while your computer was doing a high cpu task, if so, you may ask for a other benchmark test.
Usually, \'overcommitted\' procedure stop the download of new WU, and select the WU with the earliest deadline until next overcommited check, it\'s not really a problem.


To geojim
&#1488;&#1497;&#1505;&#1493;&#1512; &#1495;&#1502;&#1497;&#1491;&#1514; &#1512;&#1499;&#1493;&#1513; &#1492;&#1494;&#1493;&#1500;&#1514;.
&#1488;&#1497;&#1505;&#1493;&#1512; &#1512;&#1510;&#1497;&#1495;&#1514; &#1489;&#1503; &#1488;&#1504;&#1493;&#1513;

The reason that we\'re talking about overheating, is that if the CPU detects that the temperature is too high, it slows itself down.

Usually the only way this is obvious from the project\'s viewpoint is that the boinc benchmarks are abnormally low.

Overheating is most often a problem with laptops and systems in \'shuttle\' cases, but sometimes a fan dies or the CPU heatsink is lose on a desktop, and the same problem shows up.

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ