unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: snacktime <snacktime@gmail.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: [Mongrel] scaling unicorn
Date: Tue, 22 Jun 2010 10:30:06 -0700	[thread overview]
Message-ID: <AANLkTimMAcSSt-ieRbgGqdSljsVwWx74h191V4QIuFUK@mail.gmail.com> (raw)
In-Reply-To: <20100622001632.GA10082@dcvr.yhbt.net>

On Mon, Jun 21, 2010 at 5:16 PM, Eric Wong <normalperson@yhbt.net> wrote:
> snacktime <snacktime@gmail.com> wrote:
>> Interested in some feeback on this (does it sound right?), or maybe
>> this might be of interest to others.
>
> Hi Chris,
>
> I think you meant to post this to the mongrel-unicorn@rubyforge.org
> list, not mongrel-users@rubyforge.org :>
>
Yes, not sure how that got mixed up...


>
> That's "8 way xeon" _before_ hyperthreading, right?  Which family of
> Xeons are you using, the Pentium4-based crap or the awesome new ones?
>
Two quad core Nehalems on each server.

> How much memory is each Unicorn worker using for your app?
>
Undoubtedly this is lower then it will be under a real load, but under
our load tests they stabilize at around 160mb.

> Do you have actual performance numbers you're able to share?
> Mean/median request times/rates would be very useful.  If your requests
> run very quickly, you may be limited by contention with the accept()
> syscall on the listen socket, too.
>

I had two different types of requests to test that I did in varying
combinations.  One takes on average 600ms, and the other 40ms.  98% of
our requests will be the faster one.  Deviations were really low.

> I assume you're using nginx as the proxy, is this with Unix domain
> sockets or TCP sockets?  Unix domain sockets should give a small
> performance over TCP if it's all on the same box.
>

Yes nginx with domain sockets.


Chris
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying


      parent reply	other threads:[~2010-06-22 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTilv4e_DPDKy440xotrlE7ucFIFXs74uHyGrzCKL@mail.gmail.com>
2010-06-22  0:16 ` [Mongrel] scaling unicorn Eric Wong
2010-06-22  2:34   ` Jamie Wilkinson
2010-06-22  4:53     ` Eric Wong
2010-06-22 18:03       ` snacktime
2010-06-22 18:57         ` Jamie Wilkinson
2010-06-23  9:32         ` Eric Wong
2010-06-22 19:18       ` Jamie Wilkinson
2010-06-22 17:30   ` snacktime [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=AANLkTimMAcSSt-ieRbgGqdSljsVwWx74h191V4QIuFUK@mail.gmail.com \
    --to=snacktime@gmail.com \
    --cc=mongrel-unicorn@rubyforge.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).