Is there any way to force BOINC to ignore deadline date/times and split the time evenly between projects? At the moment the each SETI work units have about 14 day completion deadlines and take about 4 CPU hours to complete, Climate Prediction has a year deadline and is expected to take aprox 1 CPU month to complete. Both have their resource shares set to 100. What is happening is that climate prediction will run for about 1 hour then get pre-empted and SETI will then run for 4 to 8 hours before being pre-empted. As there is no problem hitting the deadlines can the system be changed to evenly split the time between the two projects?

CPU Scheduling in Ver 4.05



M7 Seti@h Berkeley's Staff Friends Club ©

If you have both projects set at 100, it will only begin to evenly split when your resource debt is balanced. Give it a week or two and it should straighten itself out.

> If you have both projects set at 100, it will only begin to evenly split when
> your resource debt is balanced. Give it a week or two and it should straighten
> itself out.
>
This answer changed from 3.x to 4.x. In 4.x the WUs start sharing nearly immediately (one hour time slices). Deadlines are completely ignored (and can be easily missed).

> > If you have both projects set at 100, it will only begin to evenly split
> when
> > your resource debt is balanced. Give it a week or two and it should
> straighten
> > itself out.
> >
> This answer changed from 3.x to 4.x. In 4.x the WUs start sharing nearly
> immediately (one hour time slices). Deadlines are completely ignored (and can
> be easily missed).
> <img> src="http://15.boinc_alpha.sig.boinc.dk?142">
>
I wasn't convinced about the deadlines but previous responses pointed to this being the problem.
The projects are still getting different amounts of processor time but I think I can see what’s causing it. I usually have one climate prediction work unit and four to six Seti work units. Seti seems to get an our for each pending work unit as well as the processing unit hence the six to one split.

> CPU Scheduling in Ver
> 4.05
>
>
>
> M7 Seti@h Berkeley's Staff Friends Club ©
>


Client scheduling policies

Seti@h Berkeley's Staff Friends Club ©

> > > If you have both projects set at 100, it will only begin to evenly
> split
> > when
> > > your resource debt is balanced. Give it a week or two and it should
> > straighten
> > > itself out.
> > >
> > This answer changed from 3.x to 4.x. In 4.x the WUs start sharing
> nearly
> > immediately (one hour time slices). Deadlines are completely ignored
> (and can
> > be easily missed).
> >