4 ms·
That is a very good point, but it's not the argument here: I'm responding specifically to the idea that webserver and webserver+fastcgi are "technically" the sa
by geocar 11y ago
That is a very good point, but it's not the argument here: I'm responding specifically to the idea that webserver and webserver+fastcgi are "technically" the same speed.
Running two web servers (one speaking HTTP and one speaking FastCGI) is necessarily going to be slower than running one web server.
This should be obvious, although it might be "not significantly slower", which is why I provided some real numbers from my experience to show at which point it becomes slower by an order of magnitude.
You might also find that it's easier to debug one webserver than two.
- hueving 11y agoI don't see how it can become an order of magnitude slower even if your app is effectively a no-op. Two extra fast cgi encodes and decodes sounds like the whole pipeline is just doing 3x the serialization of a non-fast cgi one. Am I missing some context switching overhead you are implying or something?