From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: mthread: reduce memory usage
Date: Sun, 13 Mar 2022 20:42:16 +0100 [thread overview]
Message-ID: <20220313194216.hj35X8W3K2uAkCs8WAWoiKV9BB8vsf7CABOcFrDC2M4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-222@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
There's a closed pull request on the mblaze repository
mthread: reduce memory usage
https://github.com/leahneukirchen/mblaze/pull/222
Description:
mthread keeps header data of all messages in memory until it exits without ever using it. With this change it frees the header data of each message right after processing it.
With my test data of ~100000 messages (10GB) passed to mthread with `-S` this change reduces the peak memory usage from 841MB to 27MB.
next prev parent reply other threads:[~2022-03-13 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 19:35 [PR PATCH] " julianrother
2022-03-13 19:42 ` leahneukirchen [this message]
2022-03-13 19:42 ` leahneukirchen
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=20220313194216.hj35X8W3K2uAkCs8WAWoiKV9BB8vsf7CABOcFrDC2M4@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).