Hi all,
I'm just upgraded to 6.2.14 and found out that it is not longer possible to use only one CPU on a dual core windows system.
With 5.10.45 I could change the global_prefs_override.xml to set the max_cpus to 1.
I did this in the morning to reduce the boinc load on my system and set it to 2 in the evening so that Boinc got full CPU load over night.
Then I used the command boinccmd --read_global_prefs_override to apply these changes and that worked fine.
Now with the new version I see that the file has been read but the number of used CPUs didn't change.

What has been changed here?

legolas13

---

Hi again,
I found it out.
the attribute <max_cpus>2</max_cpus> has changed to
<max_ncpus_pct>100.000000</max_ncpus_pct>

with this my mechanism to reduce the used CPUs works fine again.

---

I wonder if in this transitional period where projects have yet not adopted the % parm in their website profiles, if there is a mechanism to translate the old to new on the client side?

Nope, the preference change was done without any thought about backwards compatibility or userfriendliness.

Without any thought, really.

---

I wonder if in this transitional period where projects have yet not adopted the % parm in their website profiles, if there is a mechanism to translate the old to new on the client side?

Nope, the preference change was done without any thought about backwards compatibility or userfriendliness.

Without any thought, really.

Sadly, I agree with this comment. I may be wrong but I think users would want to specify the exact number of CPUs to use, rather than a fraction.

Also, 75% of 4 cores is 3, but what is 75% of 2 cores? Which way does it round off?
But, for me I'll just get to know the values I want and live with it.

I may be wrong but I think users would want to specify the exact number of CPUs to use, rather than a fraction.

I'm not getting in the discussion of whether it's better to have a fraction or an exact CPU count. What I disagree with is with *changing it* from the way it was before, without providing any "migration path".

---