-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Mon, 14 Jun 2004 20:26:23 GMT, Stratcat <none@no.org> wrote:

Will the projects' client's run concurrently, allowing BOINC to change the
client's use of cpu resources in the same way as Unix' 'nice' settings, or
XP's 'priority levels' via the taskmanager?

Or does BOINC determine project run percentages by simply running clients
serially, invoking individual work units one at a time?

They're currently working serially.  The actual mechanics behind this 
are potentially chaning.  The potentially new system is described here:

http://boinc.berkeley.edu/client_sched.php

If the latter, it might get a little funky w/CPDN models taking 20 - 30
days on fast machines, and 6 - 8 weeks on slower ones. And that's the time
for the current 3 phase model. They've recently added a beta 4th phase,
which forces a yet longer running model. Ostensibly, this 4th phase will
also become part of the standard model, before too long.

Rumor has it this will be handled by crunching on a CPDN unit for X 
amount of time, then before it is completed, moving on to a different 
project for X amount of time, then back to CPDN, etc, etc.

CPDN's beta is supposed to be at least another two weeks off, however, 
so we won't really know for sure until then, will we?  :-)

If a SETI unit were required to wait for a CPDN model to fully process,  it
could easily pass the current BOINC 3 week WU expiration period.

Units aren't downloaded until it is time to crunch them.  I have one box 
currently attached to four different projects (Beta, Release, and two 
Alpha projects) and as I see it, it connects, downloads units, crunches 
them, then moves on to the next project.  So, it won't download a 
SETI@Home unit then before it crunches that, do a CPDN unit.

I just wondered if you were aware of the details of how the percentage split
is implimented.

That's kinda up in the air at the moment, I think.  We'll see.

-- 
Rob                                |  If not safe,
Email and Jabber:                  |    one can never be free.
     athlonrob at axpr dot net     |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA0Oy6hm6KEoOOAe0RAixrAKDr4hk3UAfSgGbEMwpTf13AYD52iQCg3IQg
BIzzJY28xe7y2sX4hN/G0Zc=
=+hZr
-----END PGP SIGNATURE-----