Just one quick question: Why is it that BOINC switches away from tasks, even when there's only a few minutes (or seconds) left to compute? Wouldn't it be more efficient to let that task finish first?
Won't the task probably have to do some initialization again first the next time it's run, which (as I would imagine) might even take longer than the actual remaining time - or am I wrong here, is this initialization so quick that it doesn't matter?
I'm just wondering, because I got a task here with 14 seconds of remaining time...

There are projects out there with applications which run the last percent, or last minute for hours, versus those that run the last percent or minute in (almost) real time. How is BOINC to differentiate between all these applications?

And so, it won't even try to. If a checkpoint has been made and it's time to switch according to the value you set that it should switch at, BOINC will switch.

---

Thanks for the quick answer!
I guess I did think of the remaining time as somehow being the precise amount of time left to compute; but if it can vary that much, that makes it clear why there's no effort in that direction!
Thanks again and sorry for the stupid question.

Thanks again and sorry for the stupid question.

There are no stupid questions. :-)

---