Nginx & long poll: Best practices to reduce memory and bandwidth footprint

[Quintin Par]

Posting the contents inline. Can someone review this?
-----------------------------------------------------------------------------------------------------
I use nginx in this mode for [BOSH][1] and chat clients along with gzip.

location ~* /http-bind/ {
     proxy_buffering off;
     keepalive_timeout 55;
     access_log off;
     tcp_nodelay on;
     proxy_pass http://x.x.x.x:1111;
 }

Is this the best approach to **managing long polling** in nginx.

I also use just one worker process for altogether for web & chat (single
CPU). Is that fine?


  [1]: http://xmpp.org/extensions/xep-0206.html
-Quintin

On Thu, Nov 3, 2011 at 2:47 PM, Quintin Par <quintinpar at gmail.com> wrote:

> Can someone please answer this question on serverfault.com?
>
>
> http://serverfault.com/questions/327301/nginx-long-poll-best-practices-to-reduce-memory-and-bandwidth-footprint
>
>
> -Quintin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20111104/c1191e1b/attachment.html>