user/dev discussion of public-inbox itself
 help / color / Atom feed
From: Eric Wong <>
Cc: Konstantin Ryabitsev <>
Subject: how's memory usage on public-inbox-httpd?
Date: Sat, 1 Dec 2018 19:44:29 +0000
Message-ID: <20181201194429.d5aldesjkb56il5c@dcvr> (raw)

I haven't been around much, so not working on public-inbox means
fewer restarts :x

On my 2-core VM, I've been noticing public-inbox-httpd memory
spikes into the 500MB range, which is gross...  It seems caused
by slow clients and large threads/mbox downloads.  The PSGI code
only loads one email per-client in memory at-a-time when using
-httpd; but that adds up with many clients and larger messages.

I run two -httpd workers, one-per-core, but also varnish and an
experimental Ruby/C reverse-buffering proxy (yahns) for HTTPS.

The problem seems to be varnish isn't reading from -httpd fast
enough (and I lack CPU cores), but decreasing the niceness of
varnish seems to help with the problem...

             reply index

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01 19:44 Eric Wong [this message]
2019-06-06 19:04 ` Konstantin Ryabitsev
2019-06-06 20:37   ` Eric Wong
2019-06-06 21:45     ` Konstantin Ryabitsev
2019-06-06 22:10       ` Eric Wong
2019-06-06 22:19         ` Konstantin Ryabitsev
2019-06-06 22:29           ` Eric Wong
2019-06-10 10:09             ` [RFC] optionally support glibc malloc_info via SIGCONT Eric Wong
2019-06-09  8:39         ` how's memory usage on public-inbox-httpd? Eric Wong
2019-06-12 17:08           ` Eric Wong
2019-06-06 20:54   ` Eric Wong
2019-10-16 22:10   ` Eric Wong
2019-10-18 19:23     ` Konstantin Ryabitsev
2019-10-19  0:11       ` Eric Wong
2019-10-22 17:28         ` Konstantin Ryabitsev
2019-10-22 19:11           ` Eric Wong
2019-10-28 23:24         ` Eric Wong

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:

  List information:

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

  git send-email \
    --in-reply-to=20181201194429.d5aldesjkb56il5c@dcvr \ \ \ \

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

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Example config snippet for mirrors

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone