What does status Preemted mean?

CP has now stopped processing and has just downloaded another CP workunit - but has still not stated processing the new work unit.

I am running SETI and CP - both with 50% share of processing time.

This happened shortly after SETI downloaded it\'s first work units.

Si.

BOINC shares processing time in very large chunks .. on my machines that seems to translate into 15 to 20 minutes of exclusive processing on one project and then 15 to 20 minutes of processing on the next project. Projects that are waiting for processing time are placed in a "preempted" status.

So .. it's normal (but disconcerting until you see it work its way through the cycle)..

> BOINC shares processing time in very large chunks .. on my machines that seems
> to translate into 15 to 20 minutes of exclusive processing on one project and
> then 15 to 20 minutes of processing on the next project. Projects that are
> waiting for processing time are placed in a "preempted" status.
>
> So .. it's normal (but disconcerting until you see it work its way through the
> cycle)..
>

If CPDN is doing 15-20 minutes depending on your computer speed you'll never get to the next checkpoint!

> If CPDN is doing 15-20 minutes depending on your computer speed you'll never
> get to the next checkpoint!

IIRC, 1 hour is the smallest pre empt schedule.

<a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=355"><img border="0" height="80" src="http://355.cpdn.sig.boinc.dk?188"></a>

&gt; If CPDN is doing 15-20 minutes depending on your computer speed you'll never
&gt; get to the next checkpoint!

Well it's an XP 1600 running Win 2K and the sharing ratio is set at 50% Seti/CPDN. The project was reset this morning as an inplace upgrade from Win98 to Win2k seemed to make Bad Things Happen to either BOINC or the CPDN client. I saw client errors reported to the web site from that machine.

BOINC is sharing resources fairly but the time slices are being handed out in 15 to 20 minute chunks. Based on my limited experience .. this machine will probably being doing CPDN at a rate of 1.5% per day . Not sure when the checkpoints occur but a trickle event seems to happen sometime before 1.5% and credit does show up on my account.

That translates into a 60 - 70 day processing cycle per work unit though which may suck if the project goals anticipated quicker turnaround.

Open for suggestions though ....

&gt;
&gt; IIRC, 1 hour is the smallest pre empt schedule.
&gt;


Hmm ... I will take another look.

.... clipped from another thread .. in which Carl says ....

" Just be careful not to set CPDN share too low if you also have "Leave suspended tasks in memory" to "False" (the default setting), as if CPDN gets too short a time to run it will never make it to the next checkpoint (144 timesteps, which is usually 10-15 minutes "

ahhhhhhhh .... (the lightbulb goes on)

ahhh OK, found it in the code: cpu_sched_period = 3600; // 1 hour

so we're OK, the min time is an hour which should be enough to get to the next checkpoint for those who don't want the app suspended in memory

&gt; ahhh OK, found it in the code: cpu_sched_period = 3600; // 1 hour
&gt;
&gt; so we're OK, the min time is an hour which should be enough to get to the next
&gt; checkpoint for those who don't want the app suspended in memory
&gt;


Yes .. I just checked a bunch of logs and 1 hour it is (carefully inspects the bottom of the empty wine bottle for traces of ritalin ....)