Date | Commit message (Collapse) |
|
|
|
No need to expose things that don't need exposing.
|
|
This may change again in the future, but it
paves the way for simplifying this code...
|
|
This should make code review easier.
|
|
Might as well, threads are free and cheap on 64-bit
|
|
In case people try to do C10K, make life easier for them.
|
|
Thread-switching sometimes takes too long under YARV, so we
force a switch since the watchdog thread is lower-priority.
|
|
Should be fixed in 1.9.3 and/or future Kgio...
|
|
Ugh the old way was gross.
|
|
|
|
This attempts to fix all the danger associated with using
Thread#raise. Hopefully I succeeded.
Note: this logic _cannot_ be used to fix the timeout.rb
module in the Ruby standard library, that one needs to
allow nested timeouts (which seems impossible).
|
|
It's in the JoinThreads module now
|
|
|
|
They're not bad with slow clients a previously thought.
|
|
No need to obfuscate what it's doing
|
|
Run under 1.9.3dev
|
|
Fortunately it's a deprecated class that nobody
uses...
|
|
We now use IO#trysendfile in the sendfile 1.1.0 to reduce the
cost of generating backtraces for slow clients (from EAGAIN).
Nothing new for people not serving static files (but more
on the way).
Existing "sendfile" gem users must upgrade to 1.1.0
or risk being left without sendfile support at all:
http://bogomips.org/rainbows.git/patch?id=cd8a874d
|
|
IO#trysendfile does not raise exceptions for common EAGAIN
errors, making it far less expensive to use with the following
concurrency models:
* Coolio
* CoolioFiberSpawn
* Revactor
* FiberSpawn
* FiberPool
This requires the new sendfile 1.1.0 RubyGem and removes support
for the sendfile 1.0.0. All sendfile users must upgrade or be
left without sendfile(2) support. IO#sendfile behaves the same
if you're using a multi-threaded concurrency option, but we
don't detect nor use it unless IO#trysendfile exists.
|
|
It's a simpler interface and avoids allocating an array
which is nice.
|
|
Small bug fixes that have been sitting around, not much but
it's already been one month since our last release.
* Unicorn dependency updated to 3.4.0, so we get IPv6 support
and Kgio.autopush support for ":tcp_nopush => true" users.
* Optional :pool_size argument is fixed for NeverBlock and
CoolioThreadPool users.
* Mostly minor internal code cleanups
* Sunshowers support removed, it was out-of-date and
unmaintained. Cramp remains supported for now.
* X-Rainbows-* response headers support removed, nobody used it.
There are severalnew features in this release not documented
here. Consider any new features not mentioned in these release
notes to be subject to removal/renaming in future releases.
|
|
Of course some folks believe nothing in Rainbows! is :.
|
|
Actually use the Rainbows::O constant for use
[ew: rewritten commit message subject]
Acked-by: Eric Wong <normalperson@yhbt.net>
|
|
Don't need to document things that aren't ready, yet.
|
|
No need to allocate a proc every time when we can just
yield much more efficiently.
|
|
We were needlessly allocating objects even when using yield.
|
|
acceptor thread pools could use some work, still
|
|
There's a lot of code duplication here :<
|
|
Array#each will do..
|
|
Avoid constantly nuking the method cache and raising
repeated exceptions while our master process is shutting
us down.
|
|
Ugh, I need to think of a way to clean this up...
|
|
We want to use the singleton methods in Kgio to reduce
conditionals.
|
|
It's too long especially since XEpollThreadPool is planned :>
|
|
It supports IPv6 and pulls in a better Kgio. Since Unicorn
defaults to ":tcp_nopush => true", we need to flip it back
to false to be compatible with the types of apps Rainbows!
is targetted as.
|
|
Put all of our constants in one place for easy reference
|
|
Yes it's fugly
|
|
We can't work around it effectively in the C extension
itself. This requires the latest sleepy_penguin gem.
|
|
This can be a starting point for developing Cool.io or
EventMachine-based reverse proxy applications on Rainbows!
Eventually Rainbows! could replace nginx for Unicorn users!
Just don't consider this code production ready, yet, at all,
it doesn't handle any sort of failover and has no automated
tests, yet.
|
|
This allows us to more aggressively handle pipelining
as well as trigger future Kgio autopush behavior.
|
|
We should only attempt to modify the descriptor when we
block, and not for subsequent events.
|
|
Edge-triggered epoll concurrency model with blocking accept() in
a (hopefully) native thread. This is recommended over Epoll for
Ruby 1.9 users as it can workaround accept()-scalability issues
on multicore machines.
|
|
We're living on the EDGE and mixing epoll with threads :D
|
|
We'll be using this more in the future
|
|
super doesn't seem to capture arguments inside a block
under 1.8.7 :<
|
|
No reason to keep it around
|
|
We know @wr_queue is empty since we just initialized it
and the first thing an HTTP client does is read.
|
|
No need to setting an ivar for most requests
|
|
We'll override it, maybe...
|
|
We don't do Level-Triggered I/O around here
|
|
We'll lower our precision for keepalive timeouts a little
and and reduce our Time object allocation rate.
|