| commit | 37c491dcc23d445521229dbe902f02833f2a0f4c | |
| author | Eric Wong <normalperson@yhbt.net> | |
| Wed, 27 Apr 2011 20:13:24 +0000 (27 13:13 -0700) | ||
| committer | Eric Wong <normalperson@yhbt.net> | |
| Wed, 27 Apr 2011 20:30:47 +0000 (27 13:30 -0700) | ||
| tree | 86de7b439645463878eb7f506ec3e15badd7f644 | treesnapshot (tar.gz zip) |
| parent | 1b3befbadb99c83c24109f68b719276f0051c7fb | commitdiff |
examples/nginx.conf: clarify proxy_buffering for Rails 3.1
I've tested with nginx 1.0.0 and confirmed "proxy_buffering off;"
can cause Unicorn to block on a slow client reading a
large response. While there's a potential (client-visible)
performance improvement with Rails 3.1 streaming responses, it
can also hurt the server with slow clients.
Rainbows! with (ThreadSpawn or ThreadPool) is probably the best
way to do streaming responses efficiently from all angles (from
a server, client and programmer time perspective).
I've tested with nginx 1.0.0 and confirmed "proxy_buffering off;"
can cause Unicorn to block on a slow client reading a
large response. While there's a potential (client-visible)
performance improvement with Rails 3.1 streaming responses, it
can also hurt the server with slow clients.
Rainbows! with (ThreadSpawn or ThreadPool) is probably the best
way to do streaming responses efficiently from all angles (from
a server, client and programmer time perspective).
| examples/nginx.conf | diffblobblamehistory |