unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Steve Klabnik <steve@steveklabnik.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Unicorn vs Apache
Date: Mon, 11 Jul 2011 12:50:41 -0400	[thread overview]
Message-ID: <CABL+ZB67GTeO3FnTL_e7Ppr5G5Ps=FKYUBMNT6Nw94fYr7DKSQ@mail.gmail.com> (raw)
In-Reply-To: <1310400479.3665.44.camel@antium>

I only have a barely informed opinion here, but I will say two things:

1) You do know that 3.1 streaming is still very much experimental, right?

2) Introducing an additional layer in front of the application by
putting nginx in front of apache doesn't seem to be a good idea to me,
though I have done it in the past. Performance was the _last_
consideration with that application.

3) We can talk in theory all we want, but we don't have your
application. Try it, and profile. Then you'll have a real answer, not
some crap that we all make up. Especially with something like
webserver setup, you should be able to just try all these combinations
in a day or two, and see what works for your app.

There is no silver bullet.

-Steve
_______________________________________________
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


  reply	other threads:[~2011-07-11 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 16:07 Unicorn vs Apache Matt Smith
2011-07-11 16:50 ` Steve Klabnik [this message]
2011-07-11 18:50   ` Eric Wong
2011-07-11 19:22     ` Steve Klabnik
2011-07-11 18:45 ` Eric Wong
2011-07-11 18:57   ` Steve Klabnik
  -- strict thread matches above, loose matches on Subject: below --
2011-07-11 21:43 Matt Smith

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='CABL+ZB67GTeO3FnTL_e7Ppr5G5Ps=FKYUBMNT6Nw94fYr7DKSQ@mail.gmail.com' \
    --to=steve@steveklabnik.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).