From: Arjun D R <drarjun95@gmail.com>
To: supervision@list.skarnet.org
Subject: Query on s6-log and s6-supervise
Date: Tue, 8 Jun 2021 14:43:08 +0530 [thread overview]
Message-ID: <CAHJ2E==g-=8Mu8x8U99-DZbGk-uVqX5yMPp1ZD2G5tYL_9KOqA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Hi Team,
I would like to hear from you for a few queries. Please help.
1. Why do we need to have separate supervisors for producer and consumer
long run services? Is it possible to have one supervisor for both producer
and consumer, because anyhow the consumer service need not to run when the
producer is down. I can understand that s6 supervisor is meant to monitor
only one service, but why not monitor a couple of services when it is
logically valid if I am not wrong.
2. Is it possible to have a single supervisor for a bundle of services?
Like, one supervisor for a bundle (consisting of few services)?
3. Generally how many instances of s6-supervise can run? We are running
into a problem where we have 129 instances of s6-supervise that leads to
higher memory consumption. We are migrating from systemd to s6 init system
considering the light weight, but we have a lot of s6-log and s6-supervise
instances that results in higher memory usage compared to systemd. Is it
fine to have this many number of s6-supervise instances? ps_mem data -
5.5 MiB s6-log (46) , 14.3 MiB s6-supervise (129)
Thanks,
Arjun
next reply other threads:[~2021-06-08 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 9:13 Arjun D R [this message]
2021-06-08 11:04 ` Laurent Bercot
2021-06-09 2:19 ` Dewayne Geraghty
2021-06-09 3:30 ` Arjun D R
2021-06-09 8:32 ` Colin Booth
2021-06-09 11:48 ` Laurent Bercot
2021-06-10 3:54 ` Arjun D R
[not found] ` <CAHJ2E=n4+bfO39LYfGaTpaqPGtPHUSy32++4t4n+PjdZz+S=Cw@mail.gmail.com>
2021-06-09 3:40 ` Dewayne Geraghty
2021-06-09 5:01 ` Arjun D R
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHJ2E==g-=8Mu8x8U99-DZbGk-uVqX5yMPp1ZD2G5tYL_9KOqA@mail.gmail.com' \
--to=drarjun95@gmail.com \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).