I am running two projects under Boinc. SETI and Einstein. Until I upgraded, Boinc swapped projects every 60 minutes as configured. Einstein has been running for 6+ hours with no switch to SETI. SETI has 1 task that shows status of waiting to run. And several more that show ready to start. SETI tasks will resume if I pause Einstein.

Until I upgraded...

From a 6.10 or earlier version? 6.12 has fixes towards the CPU and GPU schedulers, things that were broken in previous (older) versions. So yes, it may work differently than you expect, but it's not really broken, but in reality fixed.

So please, let BOINC do the switching from now on. You will see that this will eventually work out again.

Advanced users only:
If you really can't stand it, fix these projects their debts, resetting them to zero.

You can do that by using Notepad to make a cc_config.xml file in your BOINC Data directory (where client_state.xml lives) and adding into it:

<cc_config>
<options>
<zero_debts>1</zero_debts>
</options>
</cc_config>

Save the file, as an All files, ANSI format. Check that it's called cc_config.xml, without any extra added extension.

If you had a cc_config.xml file already, add in the lines from <options> to </options>, or if those are already in place, only add in the <zero_debts> line somewhere between the <options></options> flags.

Now exit BOINC:
BOINC Manager->File->Exit->Check "Stop running science applications on Manager exit"->OK.
& restart it:
Start->(All) Programs->BOINC->BOINC Manager.

Next remove the cc_config.xml file, as you do not want to reset debts each time BOINC starts. If you have a cc_config.xml file for other uses, remove the line(s) you added and save the file again.

---

I believe from 6.10 (whatever the previous version was).
Don't understand your comment to let Boinc do the switching.
What does the parameter that is listed as time to switch between applications do?

Don't understand your comment to let Boinc do the switching.

By suspending Einstein to let Seti do work, you are deciding what is best for BOINC, you are micromanaging BOINC, while this isn't necessary.

I advise you to stop micromanaging, to set both projects on Resume and let BOINC do that switching, as it'll know better than you in the end what project has had more time on the processor than the other. All based on debt and resource share, of course.

There has been a change in the 6.10 range how BOINC decides the debt that says which project should get the CPU time next. Before that time this was totally broken, 6.10 has a fix for that. 6.12 has a further fix, but again BOINC will need to learn for itself how these things work.

This is easiest done by resetting the debt of both projects, but if you don't want to do that, then you're going to have to learn to play fingers off, or make things even worse.

---

I am using 6.12.28. it seems to switch projects ok, but it doesn't pick up the oldest WU to finish. Right now, I have 19 Collatz WU active, with two running. the oldest are due today, with 12:30, 30:06, 35:50 and 39:48 to go (minutes) respectively. those are not running. twelve other WU due 6/01 are available as well.
the running WUs are due 6/06, with 4:57 and 6:34 (hours) left to complete, respectively.

Nineteen are due 6/02, with one having completed 59 percent.

Seventeen are due 6/03, with six having completed some time

Twenty-two are due 6/04, with two having completed some time

Nine are due 6/05 - no time completed

Twenty-one are due 6/06, with six having completed some time, including the two running mentioned above

This has been going on for some time, but today is the worst I've seen.

I am using 6.12.28. it seems to switch projects ok, but it doesn't pick up the oldest WU to finish.

Please use Notepad or another clear text editor to make or edit the cc_config.xml file in your BOINC Data directory. This file needs to be made by the user, it doesn't come with BOINC.

Add into it the following:

<cc_config>
<log_flags>
<dcf_debug>1</dcf_debug>
<debt_debug>1</debt_debug>
<rr_simulation>1</rr_simulation>
<sched_op_debug>1</sched_op_debug>
<cpu_sched_debug>1</cpu_sched_debug>
<coproc_debug>1</coproc_debug>
</log_flags>
</cc_config>

Make sure you saved it into your BOINC Data directory. Default places for this directory can be found in this FAQ. Else, check your BOINC start-up messages, it'll show there as well.

Save it as cc_config.xml; check that it has only got the .xml extension, nothing else. Preferably save it in ANSI format.

Next exit BOINC;
BOINC Manager->Advanced view->File->Exit->check "Stop running science applications on Manager exit"->OK.
and restart it;
Start->(All) Programs->BOINC->BOINC Manager.

This reads in the configuration file and starts logging the extra lines. to see them, switch to Event Log (CTRL+SHIFT+E on an open BOINC Manager). Let it run for about 5 minutes, then copy the whole log to a text file, preferably zip or otherwise compress it and email it to me. I will give you my email address in PM.

Since these lines add a lot of debug information to the log, you may want to disable them for the time being, or remove the cc_config.xml file, if you don't use that for anything else. To disable the flags, use:

<cc_config>
<log_flags>
<dcf_debug>0</dcf_debug>
<debt_debug>0</debt_debug>
<rr_simulation>0</rr_simulation>
<sched_op_debug>0</sched_op_debug>
<cpu_sched_debug>0</cpu_sched_debug>
<coproc_debug>0</coproc_debug>
</log_flags>
</cc_config>

Save, exit BOINC & restart it to take effect.

---