# Scalability - using nginx with up to 300k comet connections

**URL:** <https://www.ruby-forum.com/t/scalability-using-nginx-with-up-to-300k-comet-connections/203874>\
**Category:** NGINX\
**Created:** [March 1, 2011, 3:29am UTC](https://www.ruby-forum.com/t/scalability-using-nginx-with-up-to-300k-comet-connections/203874 "2011-03-01T03:29:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [March 1, 2011, 3:29am UTC](https://www.ruby-forum.com/t/scalability-using-nginx-with-up-to-300k-comet-connections/203874/1 "2011-03-01T03:29:22Z")

</div>

Hi all,

I saw on the nginx faq that “10,000 inactive HTTP keep-alive connections  
take about 2.5M memory”  
Sounds incredibly good! I was wondering if nginx would scale to 300k  
comet connections on a single server. From the faq entry, it sounds like  
that would require 75 megs of memory, which sounds like it’d be barely  
raising a sweat.  
Our application involves holding open comet connections to about 300k  
clients, at very low per-connection messaging rates, using NHPM  
([pushmodule.slact.net](http://pushmodule.slact.net)) or whatever is the best way to use nginx with  
comet.

Would nginx be ideal for this?  
Thanks so much

Posted at Nginx Forum:

> **[Scalability - using nginx with up to 300k comet connections](https://forum.nginx.org/read.php?2,179335,179335#msg-179335)**
>
> Hi all, I saw on the nginx faq that "10,000 inactive HTTP keep-alive connections take about 2.5M memory" Sounds incredibly good! I was wondering if nginx would scale to 300k comet connections on a single server. From the faq entry, it...