Had a machine crash on me at work, and after rebuilding it, I just put it on WCG for now.  I've left that project idle for too long.  Might be putting another one up tomorrow on WCG too.

I would recommend steering clear of E@H as a back-up project, since they are having some "issues" over there. I will be investigating Rosetta at the weekend, if S@H is not better by then.

Fortunately, I hold big caches on my machines, since I do suffer connection problems, for reasons I will not go into.

FD.

There is no controll over which size task you get at E@H. There are no new shorter ones being created at this time. They may come back, and there will probably be a round of optimisations so the average crunch time will probably rise a bit more then go back down some. How much it drops depends mostly on if and how many of the short tasks they need for this run. If past runs are any indication when the optimized apps start coming out we should see a 20% to 40% drop in crunch times, it may be lower the main optimizer at that project is on the project staff now so his skills were probably used in the current app.

edit: Optimized apps come from the project at E@H, no need to bother looking for one or setting up that annoying app_info.xml file.