Xavier Noria <[email protected]> wrote: > If it is a real bad idea, is the recommendation > to Unicorn users that they should just ignore this new feature?
Another thing, Rainbows! + ThreadSpawn/ThreadPool concurrency may do the trick (without needing nginx at all). The per-client overhead of Rainbows! + threads (several hundred KB) is higher than nginx, but still much lower than Unicorn. All your Rails code must be thread-safe, though. If you use Linux, XEpollThreadPool/XEpollThreadSpawn can be worth a try, too. The cost of completely idle keepalive clients should be roughly inline with nginx. If you want to forgo thread-safety, Rainbows! + StreamResponseEpoll[1] + ForceStreaming middleware[2] may also be an option, too (needs nginx). Keep in mind that I don't know of anybody using Rainbows! for any serious sites, so there could still be major bugs :) Rainbows! http://rainbows.rubyforge.org/ [1] currently in rainbows.git, will probably be released this weekend... [2] I'll probably move this to Rainbows! instead of a Unicorn branch: http://bogomips.org/unicorn.git/tree/lib/unicorn/force_streaming.rb?h=force_streaming This is 100% untested, I've never run it. -- Eric Wong _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
