DEPLOY FAQ HACKING LICENSE NEWS README SIGNALS Sandbox Static_Files Summary TUNING Test_Suite rainbows_1 vs_Unicorn
Rainbows ActorSpawn AppPool Base Configurator Coolio CoolioThreadPool CoolioThreadSpawn DevFdResponse Epoll EventMachine FiberPool FiberSpawn MaxBody NeverBlock Rev RevFiberSpawn RevThreadPool RevThreadSpawn Revactor Sendfile ServerToken StreamResponseEpoll ThreadPool ThreadSpawn ThreadTimeout WriterThreadPool WriterThreadSpawn XEpoll XEpollThreadPool XEpollThreadSpawn

module Rainbows::XEpollThreadSpawn

This is an edge-triggered epoll concurrency model with blocking accept() in a (hopefully) native thread. This is comparable to ThreadSpawn and CoolioThreadSpawn, but is Linux-only and able to exploit "wake one" accept() behavior of a blocking accept() call when used with native threads.

This supports streaming "rack.input" and allows :pool_size tuning independently of worker_connections


This is only supported under Linux 2.6 and later kernels.

Compared to CoolioThreadSpawn

This does not buffer outgoing responses in userspace at all, meaning it can lower response latency to fast clients and also prevent starvation of other clients when reading slow disks for responses (when combined with native threads).

CoolioThreadSpawn is likely better for trickling large static files or proxying responses to slow clients, but this is likely better for fast clients.

Unlikely CoolioThreadSpawn, this supports streaming "rack.input" which is useful for reading large uploads from fast clients.

Compared to ThreadSpawn

This can maintain idle connections without the memory overhead of an idle Thread. The cost of handling/dispatching active connections is exactly the same for an equivalent number of active connections.

RubyGem Requirements

Pages Classes Methods
mail archives:
source code: git clone
	torsocks git clone http://ou63pmih66umazou.onion/rainbows.git