hmmmm just tryed that,
didn't work either

Hi Soul_keeper!
I don't know if there is a way to achieve precisely what you want, and my personal feeling is "not". But at least you must know what each parameter is doing.

"Use at most xx % of processors" is used to say how many processors Boinc will be authorized to use for everything it does (this parameter is global and ihas no relationship with projects). If you set it to 100 % your client will use your 4 processors. If you set it to anything between 75 and 99.99 % it will use only 3 processors.

What it will give to each processor depends on the Project weight of each project. As far as I know Boinc works alternatively on each of your projects for a period defined by the "Switch between applications every xxxx minutes" parameter. Since I participate to WCG only I do not know if ti is using all available processors on a single project at one time or if it is able to do this switch on a "per processor" basis. I would not be surprised though if it is the former.

In your case you should give to WCG a project weight three times that of CPDN, e.g. 3 and 1 respectively , or 75 and 25. But what it will ensure is that on the long term WCG will get three times more time than CPDN, nothing more at processor level.

To add to your puzzle, everything I have read here about this multiple grids usage said that it was particularly difficult and painful to set when one of the grids is CPDN, because of their endless tasks, knowing that Boinc waits for a checkpoint to be taken before switching a task.

Good luck. Jean.

Soul_keeper, Jean's explanation of what is going on is exactly right. What you are trying to do simply doesn't work exactly the way you want.

CPDN always messes up your debts. If you have been running it for a long time, expect your debts to be messed up. If you have been running additional projects, and trying out different BOINC versions, your debts may be damaged beyond repair.

" And I am afraid you don't want to understand it. "


is this really necessary ?





I got the info I need, (which was that those settings aren't project specific on the website, and I can't limit a project to only use 3 cores)

Can an admin please close this thread. before it deteriorates
thank you

This thread has I think all the workable suggestions to achieve what's wanted. Unless I missed it, it only requires to add the "no new tasks" to be added to the CPDN project setting in the respective client to get 1 core working permanently on CPDN and the 3 others rest on WCG... until the CPDN is ready, to permit the fetch of the next task.