[#62904] [ruby-trunk - Feature #9894] [Open] [RFC] README.EXT: document rb_gc_register_mark_object — normalperson@...
Issue #9894 has been reported by Eric Wong.
3 messages
2014/06/02
[#63321] [ANN] ElixirConf 2014 - Don't Miss Jos辿 Valim and Dave Thomas — Jim Freeze <jimfreeze@...>
Just a few more weeks until ElixirConf 2014!
6 messages
2014/06/24
[#63391] Access Modifiers (Internal Interfaces) — Daniel da Silva Ferreira <danieldasilvaferreira@...>
Hi,
3 messages
2014/06/28
[ruby-core:62911] Re: [ruby-trunk - Feature #9113] Ship Ruby for Linux with jemalloc out-of-the-box
From:
KOSAKI Motohiro <kosaki.motohiro@...>
Date:
2014-06-03 00:31:24 UTC
List:
ruby-core #62911
On Sat, May 24, 2014 at 9:48 PM, <normalperson@yhbt.net> wrote:
> Issue #9113 has been updated by Eric Wong.
>
>
> KOSAKI Motohiro <kosaki.motohiro@gmail.com> wrote:
> > Do we have only one benchmark provided by Sam? I don't think it is
> > enough much comparison to make decision.
>
> Empirical evidence on my 32-bit yahns server after running several days
> shows ~40M RSS w/ jemalloc 3.0/3.6 vs 60-80M RSS for eglibc malloc on
> Debian stable. I'll work on gathering more data for other systems.
So, I'd suggest two phase action.
1. Commit your patch, but disable by default.
2. Gather more use-case and performance data.
Note: They should be reproducible. We need measure them again and
again when libs updated.
3. Change the default when the community is convinced the benefit.