I have Rosetta at 90%, World Community Grid at 6%, and Einstein@home at 4%. Yet there are 15 World Community Grid tasks, one Einstein@home task, and *only* one Rosetta@home task "Ready to start." I don't get it. Can anyone explain, please?

Additional information: I have 8 threads, all currently running Rosetta@home tasks, with one Einstein@home task in its middle, "Waiting to run."

---

I have Rosetta at 90%, World Community Grid at 6%, and Einstein@home at 4%. Yet there are 15 World Community Grid tasks, one Einstein@home task, and *only* one Rosetta@home task "Ready to start." I don't get it. Can anyone explain, please?

Additional information: I have 8 threads, all currently running Rosetta@home tasks, with one Einstein@home task in its middle, "Waiting to run."

The weightings are not percentages but that’s as may be, as you have them adding up to 100 you can treat them as such.

But they weightings relate to jobs that are running rather than the cache of jobs ready to start. WCG does tend to download more than other projects but as they’ll be refreshed at the rate they’re used it makes little difference.

Also, the weightings apply to the total throughput over a parametrised number of days rather than controlling what it happening at each instant in time so, if you have just added WCG and Einstein then they’ll be playing catch-up for several days.

Another point is that Rosetta jobs last a lot longer than the other two so you don’t need a large cache of them to ensure that it can carry on running, it’s quite happy running one out, one in.

What cache settings do you have?

---

.

Is this what you mean?
Store at least 0.2 days of work
Store up to an additional 0.2 days of work

---

Is this what you mean?
Store at least 0.2 days of work
Store up to an additional 0.2 days of work

So that will give roughly half a day's work. As Brian posted, when you first join a project it takes a while for it to work out exactly how long it will take to process work. if the project has several different types, then it will take a while to determine how long it takes to process each type.

Having a small cache (eg 0.2 & 0.01, or even no cache) will mean less work will be downloaded initially while the new projects applications figure out how long things will take. Then the number of Tasks being processed at any given time between projects will (mostly) stabilise.

---

Grant
Darwin NT

Is this what you mean?
Store at least 0.2 days of work
Store up to an additional 0.2 days of work

Yes, and there I see the issue. Your current setting tells your BOINC client not to ask for work unless you have less than 0.2 days in your cache, BUT to ask for additional up to 0.2 days if your cache is between 0.2 and 0.4 days and this will also happen if the client connects to just to report a task.

Long story short: set it to 0.39 (store at least) and 0.01 (additional).

---

.

Thanks; I'll do that. To all of you who assumed that I have recently added projects, I have not. My signature image doesn't show World Community Grid, even though I have been contributing for months. BOINCstats doesn't include WCG.

---

BOINCstats doesn't include WCG.

It does for others. IIRC it's one of the projects, on which you need to enable data export to stats sites in your WCG preferences.

---

.

BOINCstats doesn't include WCG.

It does for others. IIRC it's one of the projects, on which you need to enable data export to stats sites in your WCG preferences.

Thanks. Updated my WCG preferences.

---

hi, you can also limit the cache size by project Calculation preferences setting

for Rosetta in my settings , i limit the disk size to 3.75GB to have 2 working WU and 2 Spare WU