initctl -- Consistently uses a large amount of CPU cycles

[Scott James Remnant]

On Wed, 2008-10-29 at 10:03 -0700, Garrett Cooper wrote:

> > reload is to reload all job definitions from disk, it's really quite
> > expensive compared to start - which just changes a job state.
> 
> What I meant is overall initctl reload uses up a large amount of
> resources; I was just wondering if there was a more lightweight
> alternative planned because we may potentially be reloading the
> configuration frequently, in such a case it wouldn't make sense to
> reload all of the files necessarily -- just the ones that have
> changed.
> 
Reload is intentionally expensive.  It is a complete flush and reload of
the internal state.

> >>  We
> >> currently use initctl reload for getting new jobs loaded into upstart
> >> init; however, I was wondering whether or not:
> >> 1. The method of getting new job definitions was the best choice.
> >>
> > Upstart should reload them itself by watching the directory with
> > inotify.
> 
> Hmm... ok. So this isn't implemented, but it's slated?
> 
This is absolutely implemented, and has been since the earliest versions
of Upstart.

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: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20081029/23a9c6f7/attachment.pgp