Suppose I run Boinc only during weekdays from 08:00-17:00, not in the weekend and the computer is switched off when Boinc is not running. I could set when Boinc runs in the Day-of-week override settings in the Processor Usage tab accordingly (Saturday and Sunday could be set to minimal time, i.e. 1 minute).
Will these settings be accounted for when new work is downloaded? I mean, when a certain project has a 3 day deadline for its work and the computer is switched off during weekends, under normal circumstances (with default Day-of-week override settings) a Wu downloaded on Thursday or Friday may/will be too late to meet the deadline.
But will the Day-of-week override settings influence the scheduler so on days before the weekend no work will be downloaded so no deadline will be missed or does the scheduler not take into account these settings?

Bart

I think, you're mixing different concepts. What you're talking about are controls that limit boinc to run within some time of day or week, whatever. Or not to run within some time.

If you don't mind boinc running swallowing all (or limited, at your option) resources between your system is started and then stopped then just leave it running. Eventually boinc will figure out resources it has on hands and would utilize those. Obviously, it can use those that are missing.

Until that evaluation would stabilize you would loose some WUs, most probably. That's the price.

---

I'm counting for science,
points just make me sick.

I'm not mixing two concepts, I was just hoping these concepts were mixed. I was not really asking this question for myself but for someone at Orbit who has problems with the short deadlines because he's running Boinc on an office computer and hates to micromanage. On my advice he already tried the Day-of-week override scheduling and came to the conclusion it doesn't work as I was hoping it would.
The Boinc-scheduler works with longer term averages but doesn't take into account scheduled times the computer is running or not, so stabilization of these parameters wouldn't lead to lifting short deadline projects over the weekend without running into deadlines.

Bart

The Boinc-scheduler works with longer term averages but doesn't take into account scheduled times the computer is running or not, so stabilization of these parameters wouldn't lead to lifting short deadline projects over the weekend without running into deadlines.

It should do this, but it takes time for BOINC to learn. I don't know how long the user tried it, but if it was less than 1 or 2 weeks, it's anyone's guess.

---

The Boinc-scheduler works with longer term averages but doesn't take into account scheduled times the computer is running or not, so stabilization of these parameters wouldn't lead to lifting short deadline projects over the weekend without running into deadlines.

It should do this, but it takes time for BOINC to learn. I don't know how long the user tried it, but if it was less than 1 or 2 weeks, it's anyone's guess.

That's surprising. I'll convey this and ask him to try a couple of weeks longer before detaching. A problem is Orbit seems to be out of work for some time (this might 'throw soot in the food' :) )

Thanks,
Bart

Well, if it's short deadline projects he wants to run, does Malaria have any work lately? Their deadlines were pretty short as well.

---

I don't think its explicitly short-deadline he wants to run, I think it's explicitly Orbit he wants to run. But if Orbit has no work he could use Malaria for testing and Boinc-learning purposes. They also have a 3-day deadline, like Orbit in its last batch. Still Malaria is a good project, so worthwhile to run anyway.

Bart

I love bionic but im having a few bugs with it.