I have been testing only Seti and CPDN in my BOINC4.13 for the past week. Changed the amount of resources share to 50% for CPDN, Seti to 25%, by removing LHC from the bunch. Effectively this translates into a 66.6% share for CPDN and 33.3% for Seti.

Yet, I have set Seti to Switch between applications every 360 minutes, while CPDN can use 120 minutes (Seti uses the Home preferences, CPDN uses the default preferences). Neither is to stay in memory when switching to the other.

I just found that CPDN has been running for over 11 hours, without switching back to Seti. So the question is, what is taking priority? The resources share, or the switch time? Or was this just a fluke?

I will be testing further with setting resources share for Seti to 50% as well.
--------------------------------
Jordâ„¢

well when it's "Global Preferences" whichever project's scheduler you last hit is how BOINC behaves. So if you did a SETI upload it would have refreshed settings from there, so it will have grabbed the 360 minutes. Although for task-switching, it appears that is the priority, so you have CPDN at 11 hrs?

At this moment resource shares are at 50-50 between the two, I have updated both Seti & CPDN so they should 'know'.

CPDN is to pre-empt after 120 minutes. Seti is to pre-empt after 360 minutes.
I just played NFS Underground 2 for the past couple of hours, so that disrupted my test as I disable BOINC when playing games, but I'll let it run through for the next couple of hours. If CPDN doesn't pre-empt within an hour and a half, something's broke.

All I did prior to getting this 'problem' was change the BOINC partition from FAT32 to NTFS. I'll keep an eye on it.

2.5 hours onwards... and it's still CPDN only that's running.

climateprediction.net - 2004-11-12 14:25:25 - Resuming computation for result 3gjf_100183026_0 using hadsm3 version 4.04
SETI@home - 2004-11-12 14:25:25 - Deferring computation for result 04mr04aa.2391.22177.442338.65_2

Local time is now 17:06 .. Seti should've kicked in 35 minutes ago.
It hasn't. Maybe I should post this on the Seti boards as well. ;)

It seemed to have been a problem with BOINC. I installed 4.54 (alpha) and immediately Seti kicked in.
--------------------------------
Jordâ„¢

<img src="http://boinc.mundayweb.com/cpdn/stats.php?userID=2&amp;trans=off">

If you had one BOINC project running before you added the second
the BOINC will run the new addition extensively until the times reach the
set percentages.

I had SETI 2 running for a long time in Beta.
Added CP and CP ran and ran and ran until
Boinc was happy it had had its share of time.

George

---

&gt; If you had one BOINC project running before you added the second
&gt; the BOINC will run the new addition extensively until the times reach the
&gt; set percentages.
&gt;
&gt; I had SETI 2 running for a long time in Beta.
&gt; Added CP and CP ran and ran and ran until
&gt; Boinc was happy it had had its share of time.
&gt;
&gt; George
&gt;
The scheduler has changed completely in 4.x. It now switches between projects on a settable schedule, and does not do any long term scheduling.

---

BOINC WIKI

&gt; At this moment resource shares are at 50-50 between the two, I have updated
&gt; both Seti &amp; CPDN so they should 'know'.
&gt;
&gt; CPDN is to pre-empt after 120 minutes. Seti is to pre-empt after 360 minutes.
&gt;
&gt; I just played NFS Underground 2 for the past couple of hours, so that
&gt; disrupted my test as I disable BOINC when playing games, but I'll let it run
&gt; through for the next couple of hours. If CPDN doesn't pre-empt within an hour
&gt; and a half, something's broke.
&gt;
&gt; All I did prior to getting this 'problem' was change the BOINC partition from
&gt; FAT32 to NTFS. I'll keep an eye on it.
&gt;
The pre-empt time is a General Setting. You only get one of these per host. You cannot set S@H to be 360 minutes and CPDN to be 120 minutes.

BOINC checks to see which project should be run at three different times that I know of: when a result is completed, when a WU is downloaded, and the preempt time after the last event that caused an evaluation of which project to run.

---

BOINC WIKI