I'm posting here because I'm certain that this is a scheduling issue, not a computation issue. I have d/l and am running BOINC 6.10.56.

I am computing for both SETI and Rosetta. I currently have 4 Rosetta WU and 1 SETI WU. Despite my request for 4 days backlog of WU, SETI is dribbling them out one at a time after the previous one finishes. But that's a SETI problem.

My 4 Rosetta WU have stats: (Elapsed HH:MM, Completion, To Do HH:MM, Due date)
15:44, 50%, 14:40, 6/1/2010
---, 0%, 26:09, 6/2/2010
---, 0%, 26:09, 6/4/2010, 5:47 PM
11:57, 27%, 25:11, 6/4/2010, 10:28 PM Running, high priority
SETI:
2:34, 37%, 3:59, 7/14/2010

I have had NO problems with the SETI WU scheduling. OTOH, I'm currently getting only one at a time, so my recent experience with it is of limited value. But once again, BOINC is scheduling the most distant Rosetta WU, at high priority, yet. 6/1 is only 5 days off, so I could easily miss the deadline, if my compute time is squandered on later due WU. I guess I should take a look on Saturday or Sunday.

I'm not sure what form to follow for a trouble report, but this is certainly one.

Ross Parlette

The Rosetta WU due 6/4/2010 10:28 PM is complete. Now the Rosetta WU due 6/4/2010 5:47 PM is Running, high priority with 23 hrs remaining. The Rosetta WU due 6/1/2010 is 79% complete with 7 hrs (estimated) remaining. I suppose it might finish in time, but the Rosetta WU due 6/2/2010 has an estimated 29 hrs processing and by all appearances, will precede the 6/1/2010 WU.

SETI is progressing normally, albeit, I'm only obtaining 1 WU at a time, and that after the previous one completes.

Perhaps the solution is to eliminate my requested backlog of 4 days. It's not working for SETI and it's counter-productive for Rosetta.

In your original post you said:

I have asked for 4 days work in advance, mostly to outlast the weekly outages at SETI.

Perhaps if you look at it from a different direction: The Rosetta WUs will get you past the SETI outages. And the current problems at SETI, which look like lasting a while.
So a shorter cache should be fine.

LB, the original reason I went w/ Rosetta was to get past the weekly outages of SETI. I've tried to be even-handed in dealing with them (locally) and Rosetta has had some outages as well, but SETI seems to be in a sort of crisis, with all sorts of problems with servers, work generation, output queues, and more than I can remember. Even setiweb.ssl.berkeley.edu is down just now. It would appear to my distant eye that more folks are willing to contribute cycles than dollars. Even in the best of times they seem to be hanging by a slender thread above the fires of Hell. And if anything goes wrong goes wrong goes wrong xxxxxx, the whole world backs up trying to get in.