gb009761, when you say that whenever you see a non _0 copy you try to shove it to the front of the queue, how exactly are you doing that? I ask because I do the same thing whenever I see a Beta task in the queue. For me, this means suspending all other tasks waiting to run, and then enough the tasks that are running, to get the ones I want to be running, running. If you have a better method, I would like to know what it is.

He wrote "Whenever I see a WU with a non _0 copy, I try to shove it to the front of the queue", i.e. anything with _1 and up as suffix. Probably for the Zero Redundant [ZR] sciences only, as for quorum 2 sciences I'd not see even the remotest benefit. Most of the cases if you get a _1 or higher, your devices is rated as fast returner anyhow, meaning in many cases the extra copy gets returned before the _0. Then you're the one waiting in the PV queue ;>). Actions for those who fancy racing the last credit into the current day :D

How: First suspend all not yet started tasks except the one you want to push. Then as second step, suspend the task(s) you want to pause to let the _1 etc ahead. Do this with LAIM on [Leave application in memory when suspended], else your tasks being interrupted are unloaded and resumed later with return to last checkpoint.

gb009761, last week when I had that intial set with quorum 2, it was basically because I didn't meet the requirements to get the quorum 1 WUs. That changed as I picked up a big cache last week and by the third day of crunching, most of my WUs since then have had quorum 1 tied to them. I hit a short run of quorum 2 WUs right after I had to abort four WUs for actiing funny, but back again for most running with quorum 1. While it is possible to take WUs and manually suspend and resume them in a way to redo the order of execution, when you have hundreds of WUs in the cache like I've had for most of the past 9 days, it just isn't too practical to manual move things around. Your technique is one I've used many times in the past to work around bottlenecks with much larger WUs from other projects, but then at most I might have 10 or so WUs in cache at one time and the manual button pushing isn't too bad. If I did it for all my CFSW WUs in cache, my fingers would have probably gone numb before I would have move things around much.

Anyway, I'm pretty close to my goal now and figure most of my quorum 2 WUs will hopefully complete with their wingmen within the next 48 hours. If not, then I may get to wait until sometime next week before my badge goes Gold - I'll probably be back to running on GFAM WUs by then since I'm only about 7 days of crunching away from that project going Gold too.

Thanks SekeRob for explaining exactly how to suspend/resume large volumes of WU's - as what you've described, is exactly the method I use.

*cough Current Jobs Completed Jobs cough* http://mindmodeling.org/beta/
But, I don't really see the point since I put enough time in reading the forums to get a pretty good idea when work is present and when not.

Edit: However, this is only some of the info that users typically ask for and it is on the front page.