From: Eric Wong <e@80x24.org>
To: rack-devel@googlegroups.com
Subject: Re: Rack and memory usage ?
Date: Thu, 27 Aug 2015 07:01:08 +0000 [thread overview]
Message-ID: <20150827070108.GA4011@dcvr.yhbt.net> (raw)
In-Reply-To: <CABGa_T83zOL=qX51J7UEpSH5nYuw7152R-x7E3qVHJ=q2j6BEg@mail.gmail.com>
James Tucker <jftucker@gmail.com> wrote:
> Well since YARV and the various GC tunings it's got a lot more heavy
> actually, and a lot more overhead and so on have landed in the stdlib (e.g.
> "packaged gems" and so on). This has a lot to do with the fact that the
> bulk of users for a long time have been running fat applications (e.g.
> rails).
Yeah. Lots of the GC speed improvements (lazy sweep, generational GC)
lead to increased memory usage. We've been trying to fight back in
ruby-core and getting ordering removed from non-Hash stuff might
promising for 2.3:
https://bugs.ruby-lang.org/issues/11414
https://bugs.ruby-lang.org/issues/11420
Lately, working again in Perl5 has gotten me to appreciate the control
afforded by reference counting :)
--
---
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2015-08-27 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 17:58 Rack and memory usage ? David Unric
2015-08-22 20:54 ` richard schneeman
2015-08-22 21:54 ` David Unric
2015-08-24 23:16 ` James Tucker
2015-08-25 12:17 ` Christian Neukirchen
2015-08-27 7:01 ` 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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150827070108.GA4011@dcvr.yhbt.net \
--to=rack-devel@googlegroups.com \
/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).