Awhile back after I made a correction to my profile, I got 100 tasks (3hrs or work or so) to run by the 18th. BOINC has not let them run at all. It keeps running my other projects. So what is it going to do? Wait until the 18th and run them?

Now BOINC is running the first one.
So the day before...how odd.

Now BOINC is running the first one.
So the day before...how odd.

Usually Boinc runs tasks on a first in first out basis, so the first task your pc gets is the first task it runs BUT when you throw in deadlines and Project Resource Share settings things get a bit wonky.. Meaning if MilkyWay sends you 300 tasks with a deadline of the 18th and your resource share is 1 then it will run them after tasks from a different project with a resource share of 50 and a deadline of the 15th. The projects with a resource share of 50 means Boinc will also try to do 50 times as much work as the project with a resource share of 1.

Personally I use resource shares from zero to 100, with the ones at 100 being tasks that are rarely available so when they do become available I can get some and the zero resource share projects as a way to only get enough tasks to fill the available cpu's or gpu's that aren't getting enough from other projects, so for instance I will run MilkyWay nbody with a resource share of 1 to run the nbody tasks but will have ie PrimeGrid with a zero resource share in case MilkyWay runs out of tasks when I need them. I also use a zero resource share when I go to a new project or type of task so I don't get 300 tasks that my pc won't run successfully. NONE of that works 100% of the time but more or less it does work for me.

All projects are of equal weight.
BOINC was downloading new material for other projects with later deadlines rather than running the tasks.

All projects are of equal weight.
BOINC was downloading new material for other projects with later deadlines rather than running the tasks.

Then it thinks you are in no danger of missing any deadlines and it can switch back to MilkyWay when it needs too.

All projects are of equal weight.
BOINC was downloading new material for other projects with later deadlines rather than running the tasks.

How many projects do you run on this computer and how large is your cache. The more projects you have, the shorter should be your cache.

---

All projects are of equal weight.
BOINC was downloading new material for other projects with later deadlines rather than running the tasks.

How many projects do you run on this computer and how large is your cache. The more projects you have, the shorter should be your cache.

9 projects of which 2 are GPU only.
Cache: .75 current and .50 extra
Should probably reduce this to .50 and .50 since I run 8-10 hours weekdays and 24/7 weekend. or 1.0 and 0

Cache: .75 current and .50 extra

The extra is the issue as it leads to a lot of extra tasks when BOINC contacts the servers, that is where you got your 100 tasks at once from. Try 0.99 + 0.01, and than lower the first as far as possible, with that amount of projects even 0.49 + 0.01 should be more than enough, but that depends actually only on your two GPU only projects. Unfortunaltely BOINC does not offer separate cache setting for CPU and GPU.

---