7 ms·
It's mostly all nice and fine with CGI until you deploy it on real world and then find that on load spike it's not 500 request / second that you can serve from
by habibur 3y ago
It's mostly all nice and fine with CGI until you deploy it on real world and then find that on load spike it's not 500 request / second that you can serve from a given box, rather it falls down to 50 request / second. The numbers are given as example only that will depend on your hardware, but the proportion is the point.
Sure you can find a single-copy-deployment solution with FCGI too like how PHP does it, but one has to feel a need first.
- zare_st 3y agoCGI is just a specification. It absolutely has nothing to do with request processing or load balancing. The web server context processing a http request passes it on via CGI to external handler. What that context is, is it a thread, is it a threadpool, is is a forked process, etc. has nothing to do with CGI itself.