Running away from something like this isn't going to help anyone. So, if you would please be so kind as to:

Make a Client_configuration (cc_config.xml) file and add into it:

320 WUs and counting, about 12 hours of work according to BOINC's own estimation... that's 0.5 days, way more than 0.01 days.

Yes, in general, for others reading here. Do know, that the scheduling code has been rewritten from the ground up. It will not go and fetch work, or schedule which projects to run, as previous versions did.

So rather than just run it for an hour, run it for 2 weeks, try to learn what it does differently. See how the new work fetch methods are now based on a low water mark and a high water mark. Find how BOINC won't immediately after uploading & reporting work ask for new work, but will only do so when it's past the low water mark.

E.g. if you wanted at least a day's worth of work:
In 6.12 and before, you'd set connect to interval to 0.01 and additional work to 1.0

In 7.0 you set minimum work buffer to 1.0 and max additional work buffer to 0.01
____________
Jord

-BOINC FAQ Service
-BOINC 7.0 FAQ

Go, seize the day, wake up and say: This is an Extraordinary life! -- Asia, An Extraordinary Life

6.x always uploaded the results almost immediately (~1min after completion). 7.x lets the results sit there by the multiple dozens for an indeterminate period of time.

Back in the early 6.x release the Min and Additional work buffer fields were set to ZERO so that projects would only get a single task - not multiple. Then you would have many tasks but only from individual projects. How can we do this in the new 7.0.25 version?

I have given you a straight and simple answer.

Want to have the difficult answer? As I posted here:

I have the same problem with version 7. Each task would complete, but BOINC Manager would not request new ones. I do not consider myself stupid, but the explanation of the parameters for minimum and maximum work buffers in the network preferences is VERY difficult to understand.

Is normal situation, for all.
The old BOINC would do work requests almost whenever it felt like it, but with BOINC 7.0 it'll wait until you reach the minimum buffer as set through the "Minimum work buffer" value. This does mean that when there's a couple of tasks in the list that have totally wrong estimates as how long they'll take, say some Seti Astropulse with an estimate of 145 hours, but they only run for 6... that BOINC can reach bottom with only as many tasks in cache as you have hardware (CPU + GPU) cores.

But anyway, the old BOINC did a "connect to" + additional work. The "connect to" was the interval with which BOINC would contact projects, while the additional work value was what extra cache you wanted. This didn't work too well, for a lot of reasons.

With BOINC 7.0 this has been changed to a Minimum work buffer + Maximum additional work buffer. Which do exactly what they say on the tin... at least when your BOINC does one project.

There's a bug in the software that sometimes rears its ugly head when more than 2 projects are attached and allowed to fetch work. As I understand it it's a difficult bug to track, and there's even the thing that when you leave BOINC well alone, eventually, after a week or what, it'll fix itself.

But you have to leave BOINC alone anyway, since this version of BOINC uses a totally new, from the ground up rewritten CPU and GPU scheduler plus work fetch module. These cannot be compared to BOINC 6's versions, they use their own values in the code and the program, which is one the reason why when you move over to 7.0 you can't easily return to 6.xx, and are the main reason why this BOINC reacts differently from previous versions.

BOINC 7 will have to learn all over again about the project's applications, their different run times, how different the estimates are from reality etc. This will take a week or more. Depends on how much your machine is on and when BOINC is allowed to do work on CPU and if applicable GPU.

By allowing BOINC to run for several days with the zero and zero days setting. BOINC 7 has a new work fetch module and new separated CPU and GPU schedulers. It will have to learn anew about how you run things. It can't do that without starting with one task per hardware core per project.

It won't do it immediately, there is no way to force it. But your BOINC 6.10 or 6.12 didn't do this immediately either, it had to learn this as well.

So if you're just willing to let go of things, not look in BOINC Manager every moment of the day what it is doing, you will eventually see that it will do things the old way. Just one task per project per core, depending on resource share and REC (the new debt).
____________
Jord

-BOINC FAQ Service
-BOINC 7.0 FAQ

Go, seize the day, wake up and say: This is an Extraordinary life! -- Asia, An Extraordinary Life