Browse files

Bump to 1.6.2

  • Loading branch information...
evanphx committed Aug 27, 2012
1 parent b2550ac commit 074adfbf4d9c735530e242a9da55889cad7624ce
Showing with 9 additions and 3 deletions.
  1. +6 −0 History.txt
  2. +1 −1 lib/puma/const.rb
  3. +2 −2 puma.gemspec
@@ -1,3 +1,9 @@
+=== 1.6.2 / 2012-08-27
+* 1 bug fix:
+ * Rescue StandardError instead of IOError to handle SystemCallErrors
+ as well as other application exceptions inside the reactor.
=== 1.6.1 / 2012-07-23
* 1 packaging bug fixed:
@@ -25,7 +25,7 @@ module Puma
# too taxing on performance.
module Const
- PUMA_VERSION = VERSION = "1.6.1".freeze
+ PUMA_VERSION = VERSION = "1.6.2".freeze
# The default number of seconds for another request within a persistent
# session.
@@ -2,11 +2,11 @@ do |s| = "puma"
- s.version = "1.6.1"
+ s.version = "1.6.2"
s.required_rubygems_version =">= 0") if s.respond_to? :required_rubygems_version=
s.authors = ["Evan Phoenix"]
- = "2012-08-12"
+ = "2012-08-27"
s.description = "Puma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](, but also works well with JRuby and MRI. Puma is intended for use in both development and production environments.\n\nUnder the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application!\n\nWith Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby.\n\nOn MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius]( or [JRuby](" = [""]
s.executables = ["puma", "pumactl"]

0 comments on commit 074adfb

Please sign in to comment.