From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: how's memory usage on public-inbox-httpd?
Date: Mon, 28 Oct 2019 23:24:50 +0000 [thread overview]
Message-ID: <20191028232450.GA26858@dcvr> (raw)
In-Reply-To: <20191019001144.GA20824@dcvr>
Eric Wong <e@80x24.org> wrote:
> Cool, but 1GB is still an order of magnitude worse that what
> I'd expect :< I remember Email::MIME had huge explosions with
> some 30MB+ spam messages:
> https://public-inbox.org/meta/20190609083918.gfr2kurah7f2hysx@dcvr/
> (maybe gmime can help)
Fwiw, I'm working on porting a scripting-language-aware malloc
tracker I wrote for another scripting language over to Perl/XS
which can track down which line of Perl called a particular
malloc() statement.
...And reading perlguts/perlxstut manpages again :x
prev parent reply other threads:[~2019-10-28 23:24 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
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 [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://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=20191028232450.GA26858@dcvr \
--to=e@80x24.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.
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).