user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: how's memory usage on public-inbox-httpd?
Date: Wed, 12 Jun 2019 17:08:15 +0000	[thread overview]
Message-ID: <20190612170815.42trclr7kfmu6ewk@dcvr> (raw)
In-Reply-To: <20190609083918.gfr2kurah7f2hysx@dcvr>

Eric Wong <e@80x24.org> wrote:
> Maybe you have bigger messages outside of LKML.
> This prints all objects >1MB in a git dir:
> 
> 	git cat-file --buffer --batch-check --batch-all-objects \
> 		--unordered | awk '$3 > 1048576 { print }'
> 
> And I also remember you're supporting non-vger lists where HTML
> mail is allowed, so that can't be good for memory use at all :<

Btw, have you had a chance to run the above to scan your repos?

The 19GB RSS would interact poorly with more frequent fork+exec;
such as the change to do unconditional expiry of long-lived
cat-file --batch* processes:

	https://public-inbox.org/meta/20190601033706.18113-2-e@80x24.org/


If you run Inline::C + PERL_INLINE_DIRECTORY to use vfork
instead of fork, then RSS won't affect process spawning
speeds.

But yeah, 19GB RSS still sucks and I'd like to get to the bottom
of it.

  reply	other threads:[~2019-06-12 17:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01 19:44 how's memory usage on public-inbox-httpd? Eric Wong
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 [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20190612170815.42trclr7kfmu6ewk@dcvr \
    --to=e@80x24.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).