From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: netd/httpd memory usage
Date: Fri, 16 Dec 2022 23:25:40 +0000 [thread overview]
Message-ID: <20221216232540.M770506@dcvr> (raw)
In-Reply-To: <20221207212013.GA25466@dcvr>
Eric Wong <e@80x24.org> wrote:
> While memory use has mostly gotten under control with scratchpad
> avoidance done around Sep (after v1.9.0), it's still higher than
> I like :<
>
> Suspiciously, PublicInbox::Smsg::load_from_data still seems to
> be causing a big chunk of long-lived allocations on my system:
OK, it doesn't seem to be a leak. At least the 4080 byte
allocations are for long-lived arenas, and it's the main
allocator.
> (or work on https://80x24.org/mwrap-perl.git to expand into C
> backtraces is required...)
Done :> (but stupid expensive :x)
> Of course, even single-threaded git packing is using massive memory
> use with the linux.git forkgroup :<
Ugh, yeah.
prev parent reply other threads:[~2022-12-16 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 21:20 netd/httpd memory usage Eric Wong
2022-12-16 23:25 ` 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=20221216232540.M770506@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).