On Tue, Apr 26, 2011 at 09:09:06PM +0200, Witold Baryluk wrote: > On 04-23 12:35, Goswin von Brederlow wrote: > > Bill Allombert <bill.allomb...@math.u-bordeaux1.fr> writes: > > > > > On Wed, Apr 20, 2011 at 09:11:59PM +0200, Raphael Hertzog wrote: > > >> (BTW, popcon is mainly run from cron so interactive performance is not so > > >> critical.) > > > > > > The issue is not interactive performances but waste of system resource. > > > Users > > > will complain. > > > > > > Cheers, > > > > Please do get real. This runs once a week at an ungodly hour. 2s or 30s > > is not going to make a collosal difference. 30s is ~0.005% of the weekly > > cpu time. Other cron jobs take far longer. And 30s is better than not > > working.
"Not working" should be quantified. I do not even know how to reproduce the warning. > Agree. I never ever even seen popcon appearing in my ps aux, when cron > triggers > daily jobs. It is always things like mandb, locate, which take LOTS > more CPU time and IO bandwidth. I never seen popcon in process list, > which always brings to me question if it works at all :) Excellent! This was a design goal, and I like to keep it that way. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
