supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <>
To: "Arjun D R" <>
Subject: Re: S6 Queries
Date: Wed, 11 Aug 2021 14:21:50 +0000	[thread overview]
Message-ID: <emb1767501-04c8-423c-84b1-37b5222a8c93@elzian> (raw)
In-Reply-To: <>

>Thanks Laurent for the detailed explanations. We did a bootup speed
>comparison between S6 and systemd. S6 is able to boot up slightly faster
>than systemd. Actual result is 4-4.5% faster but we were expecting
>something near to 20%.
>Ours is a bit complex setup with more than 140 services (includes a lot of
>long run services and a lot of dependencies). The main advantage in systemd
>is, it starts many critical processes very quickly since it has no
>dependency to logging services. We collect the logs from journalctl and
>store it in log files. Whereas in S6, the critical services start up is a
>bit delayed since it has to depend on logging services which in turn
>depends on other services (responsible for backing up the previous logs).

  Thank you for these numbers! Indeed they confirm my intuition: booting
via s6 is a little faster than systemd, but nothing extraordinary,
because s6-rc emphasizes reliability over speed.

  Your critical services may be slightly delayed, but you have the
guarantee that you will not lose logs - whereas with systemd, if a piece
of your logging system fails to start, your critical services may 
have produced some data that will vanish into the aether. Whether or not
that's an acceptable risk is up to you.


      reply	other threads:[~2021-08-11 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  4:54 Arjun D R
2021-08-02  8:27 ` Laurent Bercot
2021-08-02 18:07   ` Steve Litt
2021-08-02 19:39     ` Laurent Bercot
2021-08-02 20:42       ` Steve Litt
2021-08-02 21:40         ` Laurent Bercot
2021-08-11 11:05   ` Arjun D R
2021-08-11 14:21     ` Laurent Bercot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=emb1767501-04c8-423c-84b1-37b5222a8c93@elzian \ \ \ \
    --subject='Re: S6 Queries' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).