unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: "Bráulio Bhavamitra" <braulio@eita.org.br>
Cc: unicorn-public <unicorn-public@bogomips.org>
Subject: Re: hopefully the end of *any* OobGC
Date: Mon, 15 Sep 2014 20:35:16 +0000	[thread overview]
Message-ID: <20140915203516.GA10504@dcvr.yhbt.net> (raw)
In-Reply-To: <CAJri6_smyB0Kx1MkOyKaG=NdaBS-RQeXUKVTMC9ivYWyYYDCFQ@mail.gmail.com>

Bráulio Bhavamitra <braulio@eita.org.br> wrote:
> Eric, do you have any kind of benchmark comparing the ruby versions?

See ko1's links and benchmarks in the original page.

tl;dr: throughput is slightly worse, but performance is more
       consistent (fewer spikes).  Consistent performance is important
       for interactive use such as web servers.

> > [1] https://bugs.ruby-lang.org/issues/10137

Also, as I've told you before: please stop top-posting, sending HTML,
and using the ridiculously large signature.  These messages get seen by
hundreds, if not thousands of people and you're wasting precious
bandwidth/storage/cache space for all of them.  Paying attention to
these things is an important part of what makes unicorn work.

And FWIW, I've been spending much of the past few months applying this
philosophy to ruby-trunk and making tiny reductions in the core RubyVM
data structures here and there, slowly working up to saving several
hundreds of kilobytes in the hottest sections of memory (this will
become megabytes saved with bigger Rails apps).

There's much more work to be done, but the secondary goal of this is to
get me more acquainted with VM internals more so I can dig into less
trivial improvements.

      reply	other threads:[~2014-09-15 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 19:21 hopefully the end of *any* OobGC Eric Wong
2014-09-15 19:44 ` Bráulio Bhavamitra
2014-09-15 20:35   ` 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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140915203516.GA10504@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=braulio@eita.org.br \
    --cc=unicorn-public@bogomips.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://yhbt.net/unicorn.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).