Here is some info that might help:
Dell Studio 15 laptop. Windows 7 Home Premium. Intel Core i5.
I try changing the CPU throttle to 100%, but it's not working! It's on about 60% on the computer even though on the site it says 100%.
I have synchronized with the server many times, but it's just not working!
this particular preference can take longer to propagate than some of the others... i think in this case you might not see the change until you send in a completed workunit and get a new one...
so: what projects are you running and how long has be been? (climateprediction will take the longest for this change)
1st i should note that any changes you may have made to any preferences via your desktop software will override the website settings. and i am not sure, but it is probably the case that if you change manually *any* preference via the desktop software UI, then that computer will use *all* the local preferences instead of the web preferences.
having said that -- if you have never edited the local preferences, try this:
well, that's precisely the issue -- CPU throttle changes take a while to propagate at the moment.
two things: you might try suspending all but one task. i think the preference change will propagate at the first opportunity (ie the first task to complete after making the change at the website)
also, if you have a pressing need: it occurs to me that changes to preferences made in the desktop software are likely applied immediately. the thing is, once you've manually set preferences locally, that computer will always (i think) ignore preference changes made at the website. (i need to investigate that last point further if it's important to you.) if you have only one computer in your account this may not be a big deal; if you have a couple computers it's a bit inconvenient.
ok, expected behavior is that your computer will use settings as you define them on the website.
but: if you manually change a preference at the desktop, then this one setting will use the locally edited value in place of the web value. (...that is: a local change to a preference is taken as an "override". such overrides will be on a pref-by-pref basis: only the manually changed values will override the web settings.)
