Unfortunately members will start hitting the 1000 wu limit hardcoded in BOINC. It happens to me right now on my 32 thread machines even with the 35 per core. Increasing it to 70 per core means 16 thread machines will hit the 1000 WU limit before getting 70 per core. Anything over 70 will only help 8 threads and fewer. Relative to SCC and FAH1, most members will hit the 1000 WU limit long before they get 3 days worth of work... Smart thing might be to mix MCM in with the shorter units to get a 3 day queue.

Doubling the limit to 70 will still leave the vast majority of my machines dead in the water soon after they start the shutdown. It needs to be done away with a day or so ahead of the shutdown until it is over. Right now, the 35 wu per core limit gets me 15-26 hours of work with SCC, HSTB and FAAH selected and that's better than normal. That 35 limit has been as little as 2-3 hours of work on these same machines (Xeon chips) when FAAH or SCC had the real short WUs. A 140 limit might work if they have absolutely no issues with the move or right after it but who can guarantee that? With a PLANNED two day outage, I will want to have three days of work in each machine's queue at the start. With the 35 limit kicking back in when they come back up, my machines would simply not get any new work until they work back down under the limit in the hours after they come back up. The large majority of Linux machines will go idle during this outage, even with a 70 per core limit.

From how I read it. it's just a hardware change. I think currently WCS had there own hardware and are now are moving to "cloud"