Personally, I don't mind how many you get as long as we are aware of what the problem is. I would rather have the significant contribution towards the research. It's just not knowing what the reason is for the lack of work and the fact that it drags on for hours is slightly frustrating; but since they are working on an automated solution, I say go for it....

My understanding is that Mumps [MM] is THAT bad guy running the large Linux cluster which sucked almost all WU :-D
Is that correct?

Yes, regrettably, I believe I'd have to take the blame for this one. Good luck to everyone!

Mumps,

Welcome to posting in the forums. Yes, we did notice you had a very large number of workunit requests the past few days :) . Due to SCC and OET workunits, if they go out to Linux 64 bit AMD, they have to be validated by another machine of that type. You just had plenty to clog up the queue. We have a plan going forward to help prevent this from the future and are working to implement it now. You caught an outlier situation and like I mentioned before, we are working to resolve. As many of you can guess, the scheduler logic for sending next work units is a pretty complex issue.

Thank you everyone for your patience,
-Uplinger

Blame for what? Just continue doing what you are doing. We need the contribution to further the research. How are you to know how many is too many? Kind of like, how long is a piece of rope? Just run your configuration and let the techs handle it on the back end. It has nothing to do with little vs big user. When the feeder clogs up, big or little, you are probably not getting any work. It is what it is....