unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Sam Saffron <sam.saffron@gmail.com>
To: "Bráulio Bhavamitra" <braulio@eita.org.br>
Cc: unicorn-public <unicorn-public@bogomips.org>,
	Hitendra Hugo Melo <hitendra@riseup.net>
Subject: Re: No, passenger 5.0 is not faster than unicorn :)
Date: Wed, 3 Dec 2014 20:57:15 +1100	[thread overview]
Message-ID: <CAAtdryOQwPzBMHgCkUiAOOb81GYei9sZxbkYYwGo5-m4pMT5Hw@mail.gmail.com> (raw)
In-Reply-To: <CAAtdryN-wgOBvaYOv7moUFxsZ67Dtu+40AVMGbYCBohwE7HC8g@mail.gmail.com>

oops sent wrong link meant to send this


On Wed, Dec 3, 2014 at 8:56 PM, Sam Saffron <sam.saffron@gmail.com> wrote:
> I covered this here:
> http://discuss.topazlabs.com/t/amidst-blizzards-they-rest/1147
> it seems like an odd marketing move to me ... optimising a bit that
> needs very little help. heck ripping out hashie and the 50 frames
> omniauth injects would have a significantly bigger impact on rails
> apps out there than optimising the 0.5% that needs little optimising.
> On Wed, Dec 3, 2014 at 8:50 PM, Bráulio Bhavamitra <braulio@eita.org.br> wrote:
>> Hello all,
>> I've just tested a one instance each (one worker with unicorn and
>> --max-pool-size 1 passenger 5) on the rails app I work.
>> And the results are just as I expected, no miracle at all: Unicorn is
>> still the fatest!
>> (the difference is only a few milliseconds less per request)
>> The blocking design of unicorn is proving itself very efficient.
>> cheers!
>> bráulio

  reply	other threads:[~2014-12-03  9:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  9:50 No, passenger 5.0 is not faster than unicorn :) Bráulio Bhavamitra
2014-12-03  9:56 ` Sam Saffron
2014-12-03  9:57   ` Sam Saffron [this message]
2014-12-03 11:00 ` Hongli Lai
2014-12-03 11:05   ` Sam Saffron
2014-12-03 12:42     ` Xavier Noria
2014-12-03 14:10   ` Bráulio Bhavamitra

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:

  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=CAAtdryOQwPzBMHgCkUiAOOb81GYei9sZxbkYYwGo5-m4pMT5Hw@mail.gmail.com \
    --to=sam.saffron@gmail.com \
    --cc=braulio@eita.org.br \
    --cc=hitendra@riseup.net \
    --cc=unicorn-public@bogomips.org \


* 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


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).