Grant,

System does have 64GB of physical memory of which 80% is allotted for use by BOINC.

For now, I've enabled the option to 'Leave non-GPU tasks in memory while suspended' and will observe if this has a meaningful impact.

I will add/clarify that the application will suspend tasks...eventually...or even intermittently as soon as user input it detected as expected without that option enabled. It just wipes out progress and then picks back up at the last checkpoint which should be at 60 seconds intervals if the setting "Request tasks to checkpoint at most every 60.00 seconds" is being observed.

Thanks.

How/when checkpoints happen is very dependant on the application. In general having checkpoints at too short an interval is of no benefit, 60 minutes is generally the shortest time that is useable, otherwise the application can spend too much time preparing and recovering.
As as been suggested some applications do not do a "suspend checkpoint" if they are already stopped due the "use x% of the CPU time" option, this may apply to scheduled checkpoints, nor do all apps suspend due to load/use settings.

In reply to robsmith's message of 25 Dec 2025:

How/when checkpoints happen is very dependant on the application. In general having checkpoints at too short an interval is of no benefit, 60 minutes is generally the shortest time that is useable, otherwise the application can spend too much time preparing and recovering.

You're thinking of the "Switch between tasks every xx minutes" setting, which is a 60 minute default.
The default "Request tasks to checkpoint at most every xx seconds" is 60 seconds.



And it is just that- a request. If it can, it will; if it can't, it won't. And what Grasor is describing sounds like it's not a problem with BOINC, but the application(s).

I will add/clarify that the application will suspend tasks...eventually...or even intermittently as soon as user input it detected as expected

BOINC is requesting the Task to suspend as configured- but it is up to the application to honour that request. Some do it straightaway, others do it after a while. Some checkpoint before suspending, others don't.
It is all up to the application.

So Grasor will need to take up this issue with those projects. It's an application issue, not a BOINC issue.



In my earlier post, i did point out how he could process BOINC work without impacting on other programmes on the system without making use of the suspend functions. But as he pointed out- he;'s been doing it this way for years and isn't interested in doing it differently (even if it would do exactly what he says he wants it to do).
*shrug*

---

Grant
Darwin NT.

Update:

Performed a clean reinstallation of BOINC including removal of associated registry keys and reinstalled. Tested for about a week and the Suspend feature appears to be working as intended. As suspected, this was BOINC issue.

Grant,

In order for you to provide advice about how I can configure BOINC to work without impacting my other programs you would, in fact, need to know what the system is being used for outside of BOINC...which you do not. I understand the community would prefer that everyone donate 100% effort, but I proffer to you that the best you can get a volunteer community to pony up is their individual maximum effort. You seem to believe that your knowledge of software and hardware exceeds my own to the point that I should just "do what you say". Well, I politely and emphatically disagree. I hope you don't treat other members of this community with such open disdain. If you do, it would be best for everyone if you would click that "log off" button and move on.

Alright, enough shots fired to and fro. The problem is solved, we will never find out what caused it in the first place, probably corruption of something. You both had your shot at the other, done now.