what if native systemd service is slower than old sysvinit script?

Adam Williamson awilliam at redhat.com
Wed Sep 14 01:41:20 UTC 2011

On Tue, 2011-09-13 at 20:37 -0400, Tom Lane wrote:
> =?ISO-8859-2?Q?Micha=B3_Piotrowski?= <mkkp4x4 at gmail.com> writes:
> > 2011/9/14 Tom Lane <tgl at redhat.com>:
> >> Certainly postgresql.init was never exactly lean-and-mean, so it
> >> seems like it ought to have been doing more work than the unit file
> >> requires. Are you sure you were comparing apples to apples as far as
> >> the state of the database, kernel disk cache, etc goes?
> > I copied the service to /etc/systemd/system and changed PGDATA
> > variable, then I enabled the service and rebooted. After boot I
> > checked system boot time with systemd-analyze - I saw that it starts
> > slow, so I disabled it and deleted from /etc/systemd/system. After
> > another reboot again checked boot time with systemd-analyze.
> > I'll check tomorrow how repeatable is native service boot time.
> I'd suggest first timing some rounds of manual "service postgresql start",
> "service postgresql stop" to see what things look like without all
> the other noise involved in a system boot.

yeah; it may well be starting at a different point in the process now
it's being ordered as a systemd-native service rather than via lsb deps.

did the *overall* startup time increase by a corresponding amount?
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora

More information about the devel mailing list