good morning,

I already checked why it happens (large models, coding effort) but I think it's a pity that many tasks setting no or rarely check points and get reset after shutting down the PC in the evening and starting next working day - even with 60% progress sometimes.
I feel it's a kind of responsibility of the developer to use the resources (and money for energy by the way) as good as possible and economically - and never expect that a machine is running 24/7; especially private ones or company owned at home office.

maybe in "gods own country" energy is cheap, but not in "rest of world" ;o)
I like to support all the projects (I did years ago with a different account) but it has to make sense, not only academically also economically...

just my two cents worth
stay healthy!
Mathias

What project(s)? What operating system, what CPU/GPU hardware?
BOINC does have a setting to control checkpoints (1 minute from memory), but not every project has implemented this feature in their applications.

BOINC does have a setting to control checkpoints (1 minute from memory)

BOINC doesn't 'control' checkpoints, it 'permits' them.

A checkpoint is a collection of all the data needed for a scientific calculation to resume from the point reached so far. Sometimes that might be simple (last candidate prime checked, last candidate Collatz dis-proof): sometimes it's megabytes of data (global atmospheric state, folded protein energy levels). And it has to be consistent / coherent, ready for the algorithm to restart.

Science apps can only checkpoint when the internal data is in a state of readiness. Yes, we have to educate scientists about the need: no, we can't force them to heed our advice.

The BOINC control cited merely allows a user to say "This machine isn't usually switched off, so a checkpoint is rarely needed: you can save time and energy by not writing a checkpoint so often."

CPDN recently put out some tasks that were over 12 hours between checkpoints on my old desktop. Wouldn't be nearly so much of an issue on my ryzen that has replaced it. They then reduced this down to something like 2 hours on the same machine. I got around it by always using sleep rather than turning the machine off but know that might not always be an option for some.