Why Nginx Doesn't Implement FastCGI Multiplexing?

B.R. reallfqq-nginx at yahoo.fr
Sat Jul 20 01:25:53 UTC 2013

It is yet to prove that C10K-related problems are based on sockets/ports

The common struggling points on a machine involve multiples locations and
your harddisks, RAM & processing capabilities will be quickly overwelmed
before you lack sockets and/or ports...

If you are tempted of using enormous capacities against the struggling
points to finally achieve socket exhaustion, you are using the old
'mainframe' paradigm : few machines responsible for the whole work.
 Google proved the opposite one (several 'standard' machines working in a
cluster) was more accessible/profitable/scalable/affordable.

Could you provide some real-world-based insights on the absolute necessity
of the FastCGI multiplexing capability?

And please mind your words. Stating that someone 'clearly doesn't
understand' might be understood as calling that person 'stupid'.
That rhetorical level might lead the debate to a quick and sound end.
*B. R.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20130719/f2f660f3/attachment.html>

More information about the nginx mailing list