To keep this brief, for the time being, isn't there a setting where you can tell BOINC the WUs that are closer to their due dates should be crunched first?

---

Capitalize on this good fortune, one word can bring you round ... changes.

To keep this brief, for the time being, isn't there a setting where you can tell BOINC the WUs that are closer to their due dates should be crunched first?

BOINC will crunch in download order unless it sees deadlines approaching.

Setting "connect every 'x'" to something smallish dramatically reduces that pressure -- and I think deadlines might have been relaxed slightly as well. Of the weeks' worth of work I have cached, only one is due this month.

---

OK, put it this way. Can I set it to go for the one with the closest deadline? It'd be nice if it took into account deadline, no matter how far off; progress already made; download order. But I think the last of these might be least important. If not, why not?

[EDIT: I have quite a bit due this month after following your suggestion about caching in the other thread.]

---

Capitalize on this good fortune, one word can bring you round ... changes.

OK, put it this way. Can I set it to go for the one with the closest deadline? It'd be nice if it took into account deadline, no matter how far off; progress already made; download order. But I think the last of these might be least important. If not, why not?

[EDIT: I have quite a bit due this month after following your suggestion about caching in the other thread.]

Not possible as far as I know, and not necessary. Boinc constantly monitors the work in your cache, the dates the WUs are due, and the speed that your computer is completing work at. If it calculates that any WUs are in danger of not being completed in time, it will automatically supend the WUs it is working on and go into EDF (earliest deadline first) mode to start working on the earlier due dates. If you see some tasks listed as 'waiting to run' that is why. Boinc will also not request any new work while in EDF mode.
When the WUs that are in danger of being late are finished, Boinc goes back into standard processing order, and restarts any work that it had put into waiting status, and will also request more work if your cache needs filling.
Hope that explanation helps put you at ease.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I think what Ned said made that pretty clear.
What I am saying is, why have download order be the standard order?
You explained the bit about WUs that are in danger of not being finished in time resulting in going to EDF (earliest deadline first).
So, what I am saying is, why not go by EDF always? Or a mix of that and consideration of some WUs that have already gone through 80-90% (or more) of the crunching, when there is no danger of missing a deadline?

---

Capitalize on this good fortune, one word can bring you round ... changes.

I think what Ned said made that pretty clear.
What I am saying is, why have download order be the standard order?
You explained the bit about WUs that are in danger of not being finished in time resulting in going to EDF (earliest deadline first).
So, what I am saying is, why not go by EDF always? Or a mix of that and consideration of some WUs that have already gone through 80-90% (or more) of the crunching, when there is no danger of missing a deadline?

The problem with deadline order pops its little head up if you are doing projects like Climate Prediction, which has units that take 100's of hours to crunch, (over 1,000 on Pent M 2GHz) and a deadline of nearly a year.

Or closer to home, in Seti Beta when your RDCF is very low because you have only done MB units there and you get a AstoPulse unit with initial predicted crunch time of ~3 hrs, but which will take 50+ hrs to complete.

FYI it's BOINC that makes the decision, not the SETI or any other application. If you want this suggestion to be really looked at, you need to go over to the BOINC boards and ask.

---

My movie https://vimeo.com/manage/videos/502242

Points made. Currently I am only crunching for SETI, so I was not thinking about how this would conflict with other projects.

---

Capitalize on this good fortune, one word can bring you round ... changes.

OK, put it this way. Can I set it to go for the one with the closest deadline? It'd be nice if it took into account deadline, no matter how far off; progress already made; download order. But I think the last of these might be least important. If not, why not?

[EDIT: I have quite a bit due this month after following your suggestion about caching in the other thread.]

As far as I know, no, you can't.

I think doing the work in the order it was assigned is best: others will be doing the same work in the same order -- you want to get those back out and credited.

The other side is that long work units tend to have long deadlines, and if you do work in deadline order you'll favor the quick work units until SETI is in deadline trouble on the longer ones.

Hope that seems reasonable.

---

To keep this brief, for the time being, isn't there a setting where you can tell BOINC the WUs that are closer to their due dates should be crunched first?

You could manually suspend the tasks that you dont want running, but then you would have to keep an eye on things. Kinda a pain in the neck that way, but thats it.

---

I demand a refund. Oh wait, I didn't pay to join,
I VOLUNTEERED!

To keep this brief, for the time being, isn't there a setting where you can tell BOINC the WUs that are closer to their due dates should be crunched first?

You could manually suspend the tasks that you dont want running, but then you would have to keep an eye on things. Kinda a pain in the neck that way, but thats it.

And keep in mind, I believe that if you have any tasks maunally suspended, Boinc will not ask for any new work until you release them.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

To keep this brief, for the time being, isn't there a setting where you can tell BOINC the WUs that are closer to their due dates should be crunched first?

You could manually suspend the tasks that you dont want running, but then you would have to keep an eye on things. Kinda a pain in the neck that way, but thats it.

And keep in mind, I believe that if you have any tasks maunally suspended, Boinc will not ask for any new work until you release them.

Yes, I believe that is true.

---

I demand a refund. Oh wait, I didn't pay to join,
I VOLUNTEERED!