From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 672A51F4C0;
	Mon, 28 Oct 2019 23:24:50 +0000 (UTC)
Date: Mon, 28 Oct 2019 23:24:50 +0000
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: how's memory usage on public-inbox-httpd?
Message-ID: <20191028232450.GA26858@dcvr>
References: <20181201194429.d5aldesjkb56il5c@dcvr>
 <20190606190455.GA17362@chatter.i7.local>
 <20191016221045.GA6828@dcvr>
 <20191018192352.GH25456@chatter.i7.local>
 <20191019001144.GA20824@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20191019001144.GA20824@dcvr>
List-Id: <meta.public-inbox.org>

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