Bash completion for upstart

[Scott James Remnant]

On Sat, 2007-05-19 at 06:26 +0200, Michael Biebl wrote:

> 2007/5/18, Scott James Remnant <scott at netsplit.com>:
> > On Thu, 2007-05-03 at 12:16 +0200, Michael Biebl wrote:
> >
> > > 2007/5/3, Alex Smith <alex at alex-smith.me.uk>:
> > > > Michael Biebl wrote:
> > > > >
> > > > > I could make the start/stop completion more sophisticated, and only
> > > > > list the running jobs for stop and the stopped jobs for start. Do you
> > > > > think this would be a good feature?
> > > >
> > > > Yes, I think that would be good.
> > >
> > > Ok, updated script is attached. Though it is rather slow for stop/status.
> > > Somehow, "initctl list" can be quite slow from time to time.
> > >
> > This would be worth debugging, since initctl shouldn't be slow at all.
> > This could be a performance issue inside upstart itself.
> 
> I've run "initctl list" a hundred times and measured the execution via
> time. Attached is a log.
> As you can see, sometimes (~ 1 out of 3) I get spikes of 0.3 sec,
> which is definitely noticeable as lag.
> 
I've tried this on two different machines (x86 and x86-64) here, and
have been unable to replicate this.

The command I used was:

	for i in `seq 0 100` ; do time initctl list >/dev/null; done


I'd appreciate any help you can provide tracking this down.

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20070521/3e483a01/attachment.pgp