You clearly... err.

> 32K simultaneous active connections to the same service on a single
machine? I suspect the bottleneck is somewhere else...

I don't know what exactly "service" means in context of our conversation but if that means server then I did not say that everything should be handled by single FastCGI server. I said single Nginx server can easily dispatch thousands of HTTP requests to a number of remote FastCGI backends.

> I am no among the developers at all

That's what I thought.