I want to split the processing time over two projects. I want to set 5% on one and 95% on the other so that I have a backup project for when one of the projects goes down. I took care of this in the prefs.

However I noticed that one project always runs with all the processor time. I have more than one work unit in stock and BOINC processes the topmost work unit in the list and it seems not to care what project the work unit is for. I don't see any splitting of processing like seeing two workunits progressing with one going much faster than the other...

Anyone know what this is about and how I can correct it?

Just give at a time.
As you don't have hyperthreading, you can never have 2 WU's that are processed at the same time.

An explanation on how it is working can be find here.

Greetings from Belgium.

Help Desk: use "Most recent answer first" sorting.

Ok then how do I get project B (project a is s@h) 0% of the time so that it processes only when s@h has no work?

Bas

> Just give at a time.
> As you don't have hyperthreading, you can never have 2 WU's that are processed
> at the same time.
>
> An explanation on how it is working can be find <a> href="http://boinc.berkeley.edu/client_sched.php">here[/url].
>
> Greetings from Belgium.
> Help Desk[/i]: use "Most recent answer first" sorting.
>

> Ok then how do I get project B (project a is s@h) 0% of the time so that it
> processes only when s@h has no work?
>
> Bas

If S@H has no work and you want to have the other project at 0%, you will not process anything, is it?
Setting a project at 0% means no processing at all. Why then participating at that project, or do I understand your question in a wrong way?

> If S@H has no work and you want to have the other project at 0%, you will not
> process anything, is it?
> Setting a project at 0% means no processing at all. Why then participating at
> that project, or do I understand your question in a wrong way?

I believe he wants to use the other project as a safety net, only doing work for it when S@H is down. Otherwise, exclusively run S@H.

I believe even a setting of "0" will ask for a single WU from a project. (something to do with a work starved situation on HT CPUs)

Heffed, you understand correctly..

But a figure of 0 gives it 100 is my experience...
Anyone any ideas?

This cannot really be done at the moment. With the non-preemptive scheduler (3.x) it was possible to give a project a very small share, and it would only download work if there were none from projects with larger resource shares. Of course, it would get an occasional WU crunched if the main project never ever ran out of WUs:)

With the preemptive scheduler, you will be crunching constantly for all projects that you have signed up for, but the low resource share ones will never get credit if they have a low enough resource share. I believe that Rom is working a solution for a couple of scheduling problems including deadlines, low resource share projects and slow computers. Let's see what he comes up with.