On Tue, 2008-02-05 at 09:12 +0100, Casper.Dik at Sun.COM wrote: > I find that postrun currently is an abomination (or at least the > consumers are); it runs 10,000s of processes (literally) and takes > a long time; making it public would likely make this worse.
I find that number surprising. It shouldn't be the case and if it is, there are bugs to be fixed (probably incorrect or unnecessary scripts in the consumers). I fixed a few in some scripts in recent development builds, targetting snv_88. > Will its use be sufficiently discouraged? (And will current postrun > consumers be fixed to run more efficiently)? I think Consolidation Private is sufficiently discouraging. > I note that this is a lot worse for people who update biweekly,, > but I also wonder why postrun needs to run at standard priority? > > Some systems will run certain services faster and appear up more > quickly if postrun is run at a lower CPU priority. That's a good idea, I'll investigate. Thanks, Laca
