Maybe you can use a combination. Use Nginx location blocks to forward most requests to Unicorn, and forward the streaming URLs to Passenger Enterprise/Rainbows/Puma/etc.
On Thu, Aug 22, 2013 at 5:26 PM, Nokan Emiro <[email protected]> wrote: > Thank you for your answer Eric. > >> Using Rack::Timeout with Rainbows! instead of unicorn is probably a >> better idea. > > 99% of the requests are fast and can be served far below 300 ms. Only > a few type of requests need to stream lots of data. Do you really think that > unicorn isn't a good choice in this case and I should consider switching to > something else (Rack::Timeout + Rainbows!, Puma or whatever) just for the > sake of that 1%? > > u. > _______________________________________________ > Unicorn mailing list - [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-unicorn > Do not quote signatures (like this one) or top post when replying -- Phusion | Ruby & Rails deployment, scaling and tuning solutions Web: http://www.phusion.nl/ E-mail: [email protected] Chamber of commerce no: 08173483 (The Netherlands) _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
