From: Eric Wong <firstname.lastname@example.org>
Subject: yahns vs unicorn, part 1: overview
Date: Sun, 1 Nov 2015 09:20:53 +0000 [thread overview]
Message-ID: <20151101092053.GA5328@dcvr.yhbt.net> (raw)
yahns and unicorns are complete opposites in terms of design.
Unfortunately, comparisons between yahns and unicorn may be inevitable
since they are implemented and maintained by the same BDFL, and even
share the common HTTP parser and some code.
unicorn was only introduced in 2009, with a design which would have been
considered obsolete in 1999.
But even in 2015, implementations (even non-Ruby ones) based on
one-shot epoll/kqueue notifications like yahns are barely used
and can probably be counted on one hand.
Overview of differences:
* blocking vs non-blocking accept (yahns does the former(!))
* blocking vs non-blocking read/write
* "timeout" configurator directive can only be supported in unicorn
* slow vs fast client handling
* thread-safety, async-signal safety
More to come...
next parent reply other threads:[~2015-11-01 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151101-yahns-vs-unicorn-p@rt1>
2015-11-01 9:20 ` Eric Wong [this message]
2016-04-12 21:12 ` yahns vs unicorn, part 2: accepting connections Eric Wong
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/yahns/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).