yahns Ruby server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: ruby-talk@ruby-lang.org, yahns-public@yhbt.net
Subject: [ANN] yahns 1.9.0 -_- sleepy app server for Ruby
Date: Tue, 21 Jul 2015 20:39:06 +0000	[thread overview]
Message-ID: <20150721-yahns-1.9.0-rele@sed> (raw)

A Free Software, multi-threaded, non-blocking network application server
designed for low _idle_ power consumption.  It is primarily optimized
for applications with occasional users which see little or no traffic.
yahns currently hosts Rack/HTTP applications, but may eventually support
other application types.  Unlike some existing servers, yahns is
extremely sensitive to fatal bugs in the applications it hosts.

minor updates

  This release improves socket inheritance support.  TCP socket
  options are now applied to inherited sockets.  We also emulate
  the sd_listen_fds function to allow inheriting sockets from
  systemd.

  HTTP status strings are now generated dynamically, allowing
  applications to modify Rack::Utils::HTTP_STATUS_CODES to
  apply changes in the Rack response.  Unfortunately, this leads
  to minor (likely unnoticeable) performance regressions.

  However, our code is not optimized for Ruby 2.2+, so users on
  the latest released Ruby will benefit from reduced inline cache
  and constant lookups as we reduced our constant footprint.
  Expect further minor performance regressions if you are running
  Ruby 2.2 and earlier.

  For Ruby 2.2 users, overall performance should be largely
  unchanged from 1.7.0 to 1.8.0

  shortlog of changes since 1.7.0:

  * use opt_str_freeze for Hash#delete
  * test/helper: warn atomically
  * generate response status strings dynamically
  * reduce constants and optimize for Ruby 2.2+
  * http_response: reduce bytecode size
  * apply TCP socket options on inherited sockets
  * test/test_rack_hijack.rb: try to increase test reliability
  * emulate sd_listen_fds for systemd support
  * test/test_rack_hijack: ensure proper ordering of log messages

Please note the disclaimer:

  yahns is extremely sensitive to fatal bugs in the apps it hosts.  There
  is no (and never will be) any built-in "watchdog"-type feature to kill
  stuck processes/threads.  Each yahns process may be handling thousands
  of clients; unexpectedly killing the process will abort _all_ of those
  connections.  Lives may be lost!

  yahns hackers are not responsible for your application/library bugs.
  Use an application server which is tolerant of buggy applications
  if you cannot be bothered to fix all your fatal bugs.

* git clone git://yhbt.net/yahns
* http://yahns.yhbt.net/README
* http://yahns.yhbt.net/NEWS.atom.xml
* we only accept plain-text email yahns-public@yhbt.net
* and archive all the mail we receive: http://yhbt.net/yahns-public/

-- 
EW

                 reply	other threads:[~2015-07-21 20:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/yahns/README

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

  git send-email \
    --in-reply-to=20150721-yahns-1.9.0-rele@sed \
    --to=normalperson@yhbt.net \
    --cc=ruby-talk@ruby-lang.org \
    --cc=yahns-public@yhbt.net \
    /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 inbox:

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