I am trying to imagine the outcry you mention but I can't. An outcry that it's spam? An outcry because procedure has changed? All they would have heard from me is a big thank you for the advance warning.

I'm imagining how many are going to be upset when they do finally hear about the change. I imagine there will be comments like "I spent 10 hours searching for the cause, reinstalled Windows. Why didn't you just tell me and save me all that bother for nothing?"

I think most of our fellow members want to set and forget and be notified when important changes occur. It's the fact that some DO set and forget... they need advance warning more than anybody. Then there is another group who notice something is wrong (i.e. UD is running slower) but mistakenly think the cause lies elsewhere, for example, John Galbraith's post in this thread. At first he thought it was software he was testing. How many other fellow members are out there at this moment still thinking the problem lies elsewhere? How many will never know it's running at only 60% but would rather it run at 100%? Hoping just doesn't get the job done. An email would have accomplished much more.

The key to good relations, whether it's a marriage, an employee/employer relationship or whatever, is dialogue. It is encumbent upon BOTH partys to the relationship to identify where THEY could prevent friction in the relationship simply by uttering the appropriate words first. When 1 party expects the other to ALWAYS approach and ask for information it establishes a superior/inferior relationship. Those usually fail unless the subordinate is motivated to stay in the relationship by money, sex or fulfillment of a need to feel inferior. What is WCG offering?

It was very simple to change it once you saw that there was a lag.

All of a sudden it had used 2 hours more to get to 70% than it normaly uses to finish a WU.

How many see that? And even more important makes the connection.

This will slow things down for sure. Hope they implements the tool in the next version of the grid.

Good point, Chris_no, it would be nice if a throttle were built into UD, BOINC too. A function to read the CPU temperature sensor and display the CPU temperature would be nice too.

Sekerob, we did read the announcement carefully and if you read this thread carefully you will see that the issue is not the slowdown. The issue is that all the wonderful things you mentioned could have been accomplished with less frustration and confusion if they had done 1 simple, user-friendly thing... emailed everybody and warned in advance.

It's obvious from the read count on the announcement that less than 500 members have read that announcement. Perhaps another 500 have read repost of the announcement in other threads. So... do the math... LOTS of people still don't know about the throttle. Many of those are running slower than they need to so there is an unnecessary slowdown. Poor planning, poor communication no matter which way ya slice and dice it.

At the early hours and at this late hour i don't agree with the rbolo28 opinion on the 60% de-throttle, Basta!