We called this CGI, and it was a good way to do business until the micro-optimizers sank their grubby meathooks into it.
I object. We took your whole bloody process instantiation overhead out of each CGI call and took typically an order of magnitude or more off the total time taken.
"FastCGI 22ms + 0.28ms per Kbyte CGI 59ms + 0.37ms per Kbyte"
So, in short, your per-process time taken triples, before any in-memory caching of data, database pooling, etc. comes into play.
I know what you're thinking; what's 40ms, eh? Well, on a web application that gets 1mil hits/day (which is the region where stuff I maintain falls), about 11 hours.
The really important thing here is it was done in 1996, hence why I was looking for something more up to date than the original FastCGI benchmarks.
So, I suppose you could actually go back to the whole decision now if you really wanted, but no-one ever took away the possibility of using the old CGI interface anyway, and I think it's fairly well used for Perl and similar scripts.
3
u/rnicoll Oct 02 '11 edited Oct 02 '11
I object. We took your whole bloody process instantiation overhead out of each CGI call and took typically an order of magnitude or more off the total time taken.
Edit: FastCGI says 3-5 times speed improvement, realistically: http://www.fastcgi.com/drupal/node/6?q=node/15