supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Colin Booth <colin@heliocat.net>
To: Arjun D R <drarjun95@gmail.com>
Cc: Dewayne Geraghty <dewayne@heuristicsystems.com.au>,
	supervision@list.skarnet.org
Subject: Re: Query on s6-log and s6-supervise
Date: Wed, 9 Jun 2021 08:32:46 +0000	[thread overview]
Message-ID: <20210609083246.GA3037@cathexis.xen.prgmr.com> (raw)
In-Reply-To: <CAHJ2E=kK8JgoqCHAqNzvUZJP4PUEEZeUhp_5RcTjWep7gxt=UQ@mail.gmail.com>

On Wed, Jun 09, 2021 at 09:00:38AM +0530, Arjun D R wrote:
> Thanks Laurent for the brief detail. That really helps.
> 
> I have checked the Private_Dirty memory in "smaps" of a s6-supervise
> process and I don't see any consuming above 8kB. Just posting it here
> for reference.
> 
> grep Private_Dirty /proc/991/smaps
> Private_Dirty:         0 kB
> Private_Dirty:         4 kB
> Private_Dirty:         4 kB
> Private_Dirty:         8 kB
> Private_Dirty:         0 kB
> Private_Dirty:         0 kB
> Private_Dirty:         4 kB
> Private_Dirty:         4 kB
> Private_Dirty:         4 kB
> Private_Dirty:         0 kB
> Private_Dirty:         0 kB
> Private_Dirty:         4 kB
> Private_Dirty:         4 kB
> Private_Dirty:         0 kB
> Private_Dirty:         0 kB
> Private_Dirty:         8 kB
> Private_Dirty:         8 kB
> Private_Dirty:         8 kB
> Private_Dirty:         0 kB
> Private_Dirty:         0 kB
> Private_Dirty:         8 kB
> Private_Dirty:         4 kB
> Private_Dirty:         4 kB
> Private_Dirty:         0 kB
> Private_Dirty:         8 kB
> Private_Dirty:         4 kB
> Private_Dirty:         4 kB
> Private_Dirty:         4 kB
> Private_Dirty:         0 kB
> Private_Dirty:         0 kB
> 
... snip...
In a fully dynamic world a large number of dirty pages is expected, even
if each segment is only one or two pages. There's nothing particularly
surprising here when using a distro provided s6 that's linked
dynamically.

> 
> I have tried with flag "--enable-allstatic" and unfortunately I don't see
> any improvement. If you were mentioning about shared memory, then yes we
> are good here. It is using 2.1 MiB for 129 instances, but the private
> memory is around 12.2 MiB. I am not sure whether this is the normal value
> or not.
> 
If you're building against glibc then allstatic probably won't help. The
default config options for s6 will build with static links against all
libraries but the libc which is a pretty decent tradeoff between
efficiency and convenience, but to see super low dirty memory you'll
need to use a libc that can actually be linked statically such as musl.

For your needs, using a musl toolchain and building a fully static s6
should get you significantly better memory usage.
-- 
Colin Booth

  reply	other threads:[~2021-06-09  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08  9:13 Arjun D R
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 [this message]
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=20210609083246.GA3037@cathexis.xen.prgmr.com \
    --to=colin@heliocat.net \
    --cc=dewayne@heuristicsystems.com.au \
    --cc=drarjun95@gmail.com \
    --cc=supervision@list.skarnet.org \
    --subject='Re: Query on s6-log and s6-supervise' \
    /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

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).