I've a lot of problems with the 7.0 task scheduler.

---

Well, since I flunked Divination at Hogwarts, you'll have to give us more to go on than one sentence.

What problems?
What OS?
What version of BOINC?
Are you using a GPU?

---

Kathryn :o)

I've a lot of problems with the 7.0 task scheduler.

You can always read som in my thread.
http://boinc.berkeley.edu/dev/forum_thread.php?id=7554&sort=6

My first post was just to see if other users have similar problems.

I'm running BOINC 7.0.25 on OSX (1 host) and Windows XP (2 hosts). No GPU used.

After a few days, the only projects running are those who initially receive a large provision of work (as Climate Prediction). The other projects have 100% completed their WUs and haven't got new ones.

- There is no automatic update even if all WUs 100% complete for a project. Finished WUs remain waiting for completion for days. Manual updates are necessary to clean the queue.
- There is no automatic download of new WUs for projects waiting for work. In case of manual update, there is no new WU required even if no more work to do. To get new WUs, it's necessary to detach from the project and reattach.
- The WUs received don't respect the user-defined preferences (home/school/work) in term of applications. Non-selected applications are received even if not allowed.
- The new WUs received don't start automatically (according to time sharing). To start them, it's necessary to manually suspend the other projects.
- With multicore processors running 2 projects with equal priority, you may have all cores working on the same project for 1 hour then all cores switching to the other project, and so on, but never 50-50.

Reloading the BOINC application doesn't change anything. The only effect is the risk of loosing 100% completed WUs waiting fot completion.

I recently switched to 7.0.28 that seems to have a slightly better behaviour, especially fot Multicore processors, but the other problems remain.

---

To TRuEQ & TuVaLu
No chance to read your thread. It has been hidden by moderators.

Bernard 64250, What are your cache settings?,

Boinc 7 has a totally new rewritten scheduler, the first preference is the minimum cache setting, and the second cache setting is the maximum cache setting,
Boinc 7 will fill to the high cache setting, then wait to the low cache setting before asking for more work,
for Boinc 6 you would have used 0.01 and 3, for Boinc 7 you should use 3 and 0.01,

Claggy

2 days ago, I changed my cache settings to 4 and 0.01.

So I've got :
- 400 hours of workload for 1 project and 0 for the others on Quad Core computers.
- 200 hours of workload for 1 project and 0 for the others on Dual Core computers.

In all cases, it corresponds to 4 days * number of cores.

If their deadline is short, WUs are working in high priority. Please note that I've inherited of several pre-existing WUs when I switched to 7.0.

This may be a transient situation and I need to wait for a few days without any manual intervention to see how it evoluates.

Don't loose time. I've found a description of the bug in FAQ: BOINC 7.0.