From: Sam Saffron <sam.saffron@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: Ruby users <ruby-talk@ruby-lang.org>, mwrap-public@80x24.org
Subject: Re: [ANN] mwrap 2.0.0 mwrap - LD_PRELOAD malloc wrapper for Ruby
Date: Thu, 26 Jul 2018 15:02:59 +1000 [thread overview]
Message-ID: <CAAtdryNv726Aq=Dy7re8PZjQj080ceG22UWe0LXDohRF0Woe2Q@mail.gmail.com> (raw)
In-Reply-To: <20180726024601.ievg7jdr7blgtff6@dcvr>
Yes, this patch looks right to me.
Even if we don't have perfect fidelity here it will give absolute
clarity on "leak" vs "fragmentation related bloat". Even though
jemalloc tries hard to compensate for fragmentation bloat is still
possible.
For full context here is a dump when I started the process (it was 500meg rss)
https://transfer.sh/Q9zQS/start.txt
Here is how it looks now (1.2G rss):
https://transfer.sh/14fokY/now.txt
The script I use to generate this stuff is:
https://github.com/discourse/discourse/blob/master/script/mwrap_sidekiq
next prev parent reply other threads:[~2018-07-26 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 9:25 [PATCH] mwrap 2.0.0 mwrap - LD_PRELOAD malloc wrapper for Ruby Eric Wong
2018-07-20 9:34 ` [ANN] " Eric Wong
2018-07-26 1:36 ` Sam Saffron
2018-07-26 1:37 ` Sam Saffron
2018-07-26 2:46 ` Eric Wong
2018-07-26 5:02 ` Sam Saffron [this message]
2018-07-26 6:21 ` 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: https://80x24.org/mwrap/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAtdryNv726Aq=Dy7re8PZjQj080ceG22UWe0LXDohRF0Woe2Q@mail.gmail.com' \
--to=sam.saffron@gmail.com \
--cc=e@80x24.org \
--cc=mwrap-public@80x24.org \
--cc=ruby-talk@ruby-lang.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/mwrap.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).