# Why Nginx Doesn't Implement FastCGI Multiplexing?

**URL:** <https://www.ruby-forum.com/t/why-nginx-doesnt-implement-fastcgi-multiplexing/227266>\
**Category:** NGINX\
**Created:** [March 9, 2013, 3:44pm UTC](https://www.ruby-forum.com/t/why-nginx-doesnt-implement-fastcgi-multiplexing/227266 "2013-03-09T15:44:12Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Ji\_Zhang](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/0ea827/32.png) [@Ji\_Zhang](https://www.ruby-forum.com/u/Ji_Zhang)\
**Post date:** [July 20, 2013, 4:51am UTC](https://www.ruby-forum.com/t/why-nginx-doesnt-implement-fastcgi-multiplexing/227266/5 "2013-07-20T04:51:00Z")

</div>

Another scenario. Consider application that takes few seconds to process  
single request. In non-multiplexing mode we’re still limited to roughly  
32K  
simultaneous requests even though we could install enough backend  
servers to  
handle 64K such requests per second.

Now, imagine we can use FastCGI connection multiplexing. It could be  
just  
single connection per backend. And, again, we are able to serve roughly  
twice as many requests per second with the same hardware but little tiny  
feature called FastCGI connection multiplexing.

Posted at Nginx Forum:

> **[Re: Why Nginx Doesn't Implement FastCGI Multiplexing?](https://forum.nginx.org/read.php?2,237158,241043#msg-241043)**
>
> Hi, I'm doing some research on FastCGI recently. As I see from the FastCGI specification, it does support multiplexing through a single connection. But apparently none of the current web servers, like Nginx, Apache, or Lighttpd supports this feature....

---

_[View the full topic](https://www.ruby-forum.com/t/why-nginx-doesnt-implement-fastcgi-multiplexing/227266)._
