The newest BOINC Windows Development version has an update that will help Windows users of CPDN. When you get to a point where you are not crunching a task you may wish to update. Here is a pasted copy of the release note,

Changes in 8.0.3

Add the notion of 'strict memory bound' projects. For these projects (currently CPDN) the memory usage bound (rather than the actual working set size) will determine how many jobs are started. This avoids starting too many jobs and running out of RAM or swap space.
Don't show HTML tags in message log.
If RPC to get client versions fails, keep the old file.

I cannot understand anything you are saying in your post.

I checked and there is no 8.0.3 available for my machine -- currently running 8.0.2.in Windows 11.

I also do not understand the rest of your post either.

---

8.0.3 available to download for Windows here

Older versions of BOINC assume the memory used by a task is the same as what they start off using. The new version checks the maximum allowed in the configuration file so preventing problems with OIFS tasks when too many tasks are running and memory usage ramps up dramatically.

Note the development version will have daily changes. Certainly the Linux version does as I get notifications from apt to that effect.

It's important to note that this new 'feature' in the boinc client is not enabled by default. It was found to cause problems for other projects that didn't set appropriate values of the rsc_memory_bound in the task XML as CPDN does, as our tasks need significant memory.

For that reason, the new feature has to be to enabled by the project in the XML sent with the task. CPDN have not yet tested this to see if it behaves in the way we hope it will. So don't feel a need to rush and install this new version as I doubt any other project (maybe LHC) are likely to enable this feature. For the time being, the CPDN scheduler is set to restrict the number of tasks in progress as a workaround (as LHC do). We can't change this until the new client is in widespread use.

---

---
CPDN Visiting Scientist

. We can't change this until the new client is in widespread use.

So not till the feature is in a stable release I am guessing, might even have to wait till the package managers pick it up. They are usually at least one or two behind the latest stable release.

Yes, it'll be a long wait before we can confidently make a change. There's no mechanism by which I could do this in the task: if ( client_version > 8.0.2 ) do this, else do that. Be nice if there was. Unless someone knows different....

---

---
CPDN Visiting Scientist