Check your profile on the web page. The default is 4. You will need to change the number in the profile you have selected to 6.

Cheers

With 6.2.28 the overriding function is the number of processors on the web profile, even though the local preferences may indicate 100%. With later clients, the % processors is the only setting the client is supposed to respond to. The default for a brand new profile/member is now actually 16 or 32 processors aka cores/threads (BOINC really has no limits on how many it can manage [but resources].

Let us know, then when OK, please edit/insert [RESOLVED] in the opening post title, so we all know the case is closed.

cheers

--//--

No worries... it's really a deprecated parm and limited to just work for that 6.2.28 build. WCG has also set the daily quota to max out at 32 processors, at 120 per core [latest I understand it to be v.v. reliability ratings]. Don't think there are devices that are able to eat 32x120 units a day of any present sciences, with the exception of maybe DDDT2 C-Type, but these are on trickle anyhow... hard to get enough to crunch exclusively :(

If GPU crunching becomes real, that number might have to be reviewed, at < 5 minute a piece [but I understand there will be 5 or more targets packed in a HCC GPU work-unit to get a runtime extension]. Since 32 threads of parallel processing takes huge resource, WCG is looking at multithreaded for new sciences that come along [if they can, it being an art in itself to program]. 1 task over 6 cores or 6 on 6 cores in this case [or any number of threads that settings would allow this to be limited to] If and when it comes, WCG will surely have worked out the efficiency issues that come with that territory.

--//--