I've downloaded and am running BOINC v 5.6.5. I really need the CPU limiting feature, due to the latest version of DisKeeper not starting ever when the CPU is at 100%. I've tried this version as a client install and a service install, and I've done the update for preferences and waited, but the CPU still remains at 100%.

I don't know what I'm missing; any help appreciated.

---

Did you change your preferences at a project site and then update through the manager?

Note: If your trying change your preference setting at Seti it won't work. The server are not updating Boinc properly at the moment. Try updating your preferences at a different project, or if you feel up to it, edit your global_prefs.xml file manually. A Boinc restart will be required for it to take.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

I changed my preferences thru the BOINC manager which took me to the SETI preferences page. If SETI does not support this, is this a bug that is being worked on? What other projects do support the CPU limiting feature? Also, I'm unable to find the global_prefs.xml file anywhere in the BOINC directory structure.

Thanks, Henry

---

I attached to another project (Einstein) and it created the global prefs file. I was able to edit as advised. Thanks for the help!

---

I was a member ages ago - but 100% usage burned out my lap top fan.
I'm back, with manager 5.6.5 and rosetta@home project, was able to set to 60% OK.
However, application only runs for a few minutes, then stops, I have to suspend/resume, or sometimes exit/restart Boinc manager. Application then picks up where it was, and runs for a few minutes again. My preferences have it set to run all the time (I think) but it seems to keep stopping on it's own.
Mike

---

I was a member ages ago - but 100% usage burned out my lap top fan.
I'm back, with manager 5.6.5 and rosetta@home project, was able to set to 60% OK.
However, application only runs for a few minutes, then stops, I have to suspend/resume, or sometimes exit/restart Boinc manager. Application then picks up where it was, and runs for a few minutes again. My preferences have it set to run all the time (I think) but it seems to keep stopping on it's own.
Mike

BOINC's CPU throttle is pretty course. It can only work with 1 second blocks. Is it possible that this is causing what you are seeing?

---

BOINC WIKI

BOINCing since 2002/12/8

I was a member ages ago - but 100% usage burned out my lap top fan.
I'm back, with manager 5.6.5 and rosetta@home project, was able to set to 60% OK.
However, application only runs for a few minutes, then stops, I have to suspend/resume, or sometimes exit/restart Boinc manager. Application then picks up where it was, and runs for a few minutes again. My preferences have it set to run all the time (I think) but it seems to keep stopping on it's own.
Mike

BOINC's CPU throttle is pretty course. It can only work with 1 second blocks. Is it possible that this is causing what you are seeing?

?? No, it runs for a few minutes, then stops for several minutes. Not seconds. So - I restart it, same problem. While it ususally picks up where it left off, on occasion the completion of the application has suddenly gone from 1-2% up to 100%. Which of course sends as completed, up to BOINC/Rosetta land. Loaded BOINC 5.7.1, same good CPU throttling, same problems. I'd rather not downgrade and use Threadmaster (sp?) but maybe that's a better choice. Or - is there a specific message thread discussing these BETA versions?
thanks
Mike

---

Or - is there a specific message thread discussing these BETA versions?

Here, I made one. :)

---

Or - is there a specific message thread discussing these BETA versions?

Here, I made one. :)

Excellent - I'll post there. thanks

---

I've downloaded and am running BOINC v 5.6.5. I really need the CPU limiting feature, due to the latest version of DisKeeper not starting ever when the CPU is at 100%. I've tried this version as a client install and a service install, and I've done the update for preferences and waited, but the CPU still remains at 100%.

I don't know what I'm missing; any help appreciated.

Surely there is a more technological approach than mine, but I just use the start/stop settings to only do work between 4:00 and 2:00 in general preferences.

InvisiTasking can do it's work in the 2 hours of idle time between 2am and 4am.

---

I've downloaded and am running BOINC v 5.6.5. I really need the CPU limiting feature, due to the latest version of DisKeeper not starting ever when the CPU is at 100%. I've tried this version as a client install and a service install, and I've done the update for preferences and waited, but the CPU still remains at 100%.

I don't know what I'm missing; any help appreciated.

Surely there is a more technological approach than mine, but I just use the start/stop settings to only do work between 4:00 and 2:00 in general preferences.

InvisiTasking can do it's work in the 2 hours of idle time between 2am and 4am.

That works. I have mine set up like that for the nightly AV scan. But I use the throttling to keep my lappy a bit cooler too.

---

Kathryn :o)

Boinc is using 99% of my CPU making my computer to slow to use. What should I do? I am not real tech savvy.)

---

Boinc is using 99% of my CPU making my computer to slow to use. What should I do? I am not real tech savvy.)

BOINC is designed to use unused computer cycles. It runs at the lowest priority so it should release to whatever you need it to. That said, if you are low on RAM it can bog things down due to paging and the like.

If you have enough RAM (requirements vary by project) and you want to limit how many cycles BOINC uses, then you can download the current alpha release of the client. Do this at your own risk. It is alpha software and it still has bugs. Hopefully it will become the stable release in another few weeks. It's also possible to limit RAM usage through the web interface on Seti@Home (I don't know what other projects have updated server software for that to be shown) but that also only works with the current alpha client.

---

Kathryn :o)

David, disable the screensaver if you haven't done this already.

---

David, disable the screensaver if you haven't done this already.

::slaps self on head::

Doh.

Thanks Mo.

---

Kathryn :o)