No, I'm not making a political statement; I'm making a technical complaint.

I added predictor@home (Yes, I know you're not responsible for that!) a couple of days ago when I was out of SETI workunits and the server was unable to supply any (BOIC repeatedly connected, and failed to get work units) and figured my computer might as well do something useful. It's set for Seti 100, Predictor 50 "priority" or whatever. On the Projects tab of BOINC it shows Predictor getting 33.33% of the resources and SETI 66.67%, as expected.

However, since I got Predictor in, BOINC has never once attempted to connect to the SETI scheduler to get workunits (according to the messages logged in that tab). Resetting the project and rebooting have had no effect.

I *believe* this is a BOINC issue, from the looks of it; nothing Predictor does *should* be able to steal 100% of the resources when I've told BOINC to give it 33%.

This is due to the resource debt created when you first add a project. Give your system a a few days/week or so to level out the projects and then it should continue to pull down work units from both projects as your resource share is set out.

Jamie

> This is due to the resource debt created when you first add a project. Give
> your system a a few days/week or so to level out the projects and then it
> should continue to pull down work units from both projects as your resource
> share is set out.
>
> Jamie
>
Good answer but the time frame should be 1 to 4 weeks.

John Keck
BOINCing since 2002/12/08

> > This is due to the resource debt created when you first add a project.
> Give
> > your system a a few days/week or so to level out the projects and then
> it
> > should continue to pull down work units from both projects as your
> resource
> > share is set out.
> >
> > Jamie
> >
> Good answer but the time frame should be 1 to 4 weeks.
>
John Keck
> BOINCing since 2002/12/08
>

ok thanks for correcting me :D

What I did to solve part of this problem is set 2 different prefernces for the computers.

On Seti
Set home preferences to cache some larger number of days
set computer on seti to use home

On Predictor
Set school prefences to cache a fraction of a day
set computer on predictor to use school

That way predictor does not cache to many predictor units. That way I get units from 1 of the projects, but not too many from predictor. This seems to get thru some of the short outages. The only negative side is when we have WU shortages some days I get mostly predictor units. With this setting I am switching projects, but mainly seti when available.

Now if what I have read for Boinc 4.0 it may solve the problem for multiple projects...Lets only hope... But of course I have only read from unofficial sources.