I've noticed that the manager (7.0.14) ignores the change projects every xx minutes. I think the default is 60 minutes. However, every task which starts will run until it's finished without switching to another project. An exception to this behaviour are tasks of 20+ hours runtime. Those switch after 8-12 hours. Nevertheless, none of the tasks honoured the setting of 60 minutes even though there were more than 6 projects in the work cache.

i think the 'Switch between tasks every 60 minutes' setting is a setting that stops Boinc switching too often, Not a compulsory you must switch every 60 minutes setting, if Boinc doesn't need to switch (because it's paying back debt) it won't,

Claggy

Depends on which project ran, how much debt it had gathered towards the other projects, whether the tasks ran in high priority and most importantly if the app does checkpoints. When the app doesn't checkpoint, tasks will run from start to finish without let-up.

---

Remember that with BOINC v7.x.xx, we can't use the word 'debt' any more - at least, not in the old time-based units that we're familiar with. Even the <debt_debug> logging flag doesn't work any more, having been changed to <priority_debug> ([trac]changeset:24429[/trac]).

Scheduling priority is now determined by credit awarded by projects, rather than by time. It's written up in http://boinc.berkeley.edu/trac/wiki/ClientSchedOctTen and http://boinc.berkeley.edu/trac/wiki/ClientSched, but no - I don't understand it either.

But I'm seeing something similar. I have a machine with CPU tasks waiting to run, but which are never getting scheduled. They've been sitting there, waiting, for five days now. Their original deadline was 14 days, so they're now down to 9 days. I'll wait and see if they're held back until high priority running becomes necessary, and try to remember to watch the priority logs in the meantime.