From 598525843ee1d120fd9878011ca2b6328c2cf95f Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 9 May 2011 02:24:26 +0000 Subject: doc: better document :pool_size options CoolioThreadPool has had it supported forever, but only NeverBlock had it documented. --- lib/rainbows/xepoll_thread_pool.rb | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) (limited to 'lib/rainbows/xepoll_thread_pool.rb') diff --git a/lib/rainbows/xepoll_thread_pool.rb b/lib/rainbows/xepoll_thread_pool.rb index 9107b5d..c1605b8 100644 --- a/lib/rainbows/xepoll_thread_pool.rb +++ b/lib/rainbows/xepoll_thread_pool.rb @@ -39,9 +39,24 @@ require "raindrops" # exactly the same for an equivalent number of active connections # (but independently tunable). # -# Since +:pool_size+ and +worker_connections+ is independently tunable, +# === :pool_size vs worker_connections +# +# Since +:pool_size+ and +worker_connections+ are independently tunable, # it is possible to get into situations where active connections need # to wait for an idle thread in the thread pool before being processed +# +# In your Rainbows! config block, you may specify a Thread pool size +# to limit your application concurrency independently of +# worker_connections. +# +# Rainbows! do +# use :XEpollThreadPool, :pool_size => 50 +# worker_connections 100 +# end +# +# In extremely rare cases, this may be combined with Rainbows::AppPool +# if you have different concurrency capabilities for different parts of +# your Rack application. module Rainbows::XEpollThreadPool extend Rainbows::PoolSize -- cgit v1.2.3-24-ge0c7