Whyyyyyyyyyyyyy don't we have 2 settings for cpu%???

I can handle 40% while i'm running but
I want it at 100% when idle.

Don't gray out the idle time when 'when computer is in use' is checked and
add a second %

You'd get alot more out of us.

And now you want money?
use your resources better folks.

---

The CPU% is mainly intended for when a computer's CPU is overheating, and shouldn't affect the behaviour of the system when it is in use.

Boinc runs at a very low priority (nice 19 in Linux, or the equivalent in Windows), and hence the operating system will immediately take over if any other task comes along.

The most common reason for a system being affected by Boinc is when there is contention for memory, and this won't be affected by the user's CPU% setting since the jobs stay in memory when being throttled.

---

And now you want money?
use your resources better folks.

BOINC developers aren't asking for your money. They're paid through the NSF, which gives out grants to projects that are interesting enough to be given money to.

Initial grant given
Continued grant

Individual projects can also get grants, if interesting enough, like Einstein@Home's grant.

---

There are times when BOINC or the client takes 100% cpu; only the client runs at low priority, boinc and boincmgr are normal.

True, it is seti that emails me for donations; to me, seti is boinc.

The percentage may be for overheating, originally, but like i'm showing, they can get more work from some of us if they do a couple of changes.
--- quote "open your miiiiiiiiiind, open your miiiiiiiiiiiiiind"

:)

---

There are times when BOINC or the client takes 100% cpu

Do you have hundreds of workunits on your cache?

Benchmarks don't really count. I think they're already done in low priority; you just don't see that on task manager.

---

Really? BOINC.exe is loaded in normal priority (on windows).

I said "you just don't see that on task manager". Task manager doesn't show priorities for individual threads.

---

and they're not

They are.

as far as i can see.

Exactly, you can't see it with Task Manager.

boinc.exe process = normal priority
thread within boinc.exe handling everything (scheduler, file transfers, communication with apps, etc) = normal priority
thread within boinc.exe doing benchmarks = low priority

Task manager shows only process priority, not priorities of individual threads. Sysinternals Process Explorer, for example, can show thread priorities.

---