This is an edge-triggered epoll concurrency model with blocking accept() in a (hopefully) native thread. This is comparable to
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
This is only supported under Linux 2.6 and later kernels.
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.
CoolioThreadSpawn, this supports streaming "rack.input" which is useful for reading large uploads from fast clients.
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.
raindrops 0.6.0 or later
sleepy_penguin 3.0.1 or later
mail archives: https://yhbt.net/rainbows-public/ http://ou63pmih66umazou.onion/rainbows-public/ nntp://news.public-inbox.org/inbox.comp.lang.ruby.rainbows nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.rainbows nntp://news.gmane.io/gmane.comp.lang.ruby.rainbows.general public: firstname.lastname@example.org source code: git clone https://yhbt.net/rainbows.git torsocks git clone http://ou63pmih66umazou.onion/rainbows.git