Download
Johannes,
Thank you very much for your hard work and kind contribution to the internet! :-)
I hope to try this later today.
OK, I wrote a big post explaining why this is important (for those asking questions) but when I posted it, I had been logged out automatically somehow and now it's all gone. 1 hour of my life gone... :-(
Briefly:
1. PHP and GS could have undiscovered security risks - they've had them in the past, why not again? Why take risks if they are totally unnecessary for your usage case / situation? If your business depends on a site, why add risks of hacking?
2. Speed of PHP vs. HTML, particularly, PHP without a clever caching arrangement. Look here:
http://www.martinsikora.com/load-time-of...-php-pages
http://www.webhostingtalk.com/showthread.php?t=619396
http://forum.gwan.com/index.php?p=/discu...ighttpd/p1
http://stackoverflow.com/questions/14971...html-speed (first answer suggests a 10-1 difference between the simplest possible HTML and PHP scripts maximum responses per second. I've also seen a 50% reduction in serve time referred to for the same experiment, elsewhere).
3. Avoiding PHP means a simpler server like nginx or G-Wan can be used. Potentially you can be talking 200kB rather than 200MB depending on OS, httpd and PHP setup, 6x less memory under high load, and 2x more requests/second just from this factor alone. Look here:
http://nbonvin.wordpress.com/2011/03/24/...er-to-use/
4. Faster pages = higher Google pagerank, happier viewers. Every millisecond counts (for some websites).
5. Avoiding PHP/apache means much less memory usage - cheaper VPS/Amazon costs. Or, it means you can cache absolutely everything in physical RAM for ultra-fast speeds, vs hitting the disk filesystem or virtual memory on your VPS slice.
6. Continually watching out for security updates is a drain on my 'attention' as a sysadmin. I'd rather avoid it.
7. Just for fun: http://www.amazon.com/dp/0596529309/?tag...verfl08-20
Also check out http://load-impact.com - lets you stress test your site.
Example here: http://www.webandblog.com/reviews/apache...eavy-load/
Thank you very much for your hard work and kind contribution to the internet! :-)
I hope to try this later today.
OK, I wrote a big post explaining why this is important (for those asking questions) but when I posted it, I had been logged out automatically somehow and now it's all gone. 1 hour of my life gone... :-(
Briefly:
1. PHP and GS could have undiscovered security risks - they've had them in the past, why not again? Why take risks if they are totally unnecessary for your usage case / situation? If your business depends on a site, why add risks of hacking?
2. Speed of PHP vs. HTML, particularly, PHP without a clever caching arrangement. Look here:
http://www.martinsikora.com/load-time-of...-php-pages
http://www.webhostingtalk.com/showthread.php?t=619396
http://forum.gwan.com/index.php?p=/discu...ighttpd/p1
http://stackoverflow.com/questions/14971...html-speed (first answer suggests a 10-1 difference between the simplest possible HTML and PHP scripts maximum responses per second. I've also seen a 50% reduction in serve time referred to for the same experiment, elsewhere).
3. Avoiding PHP means a simpler server like nginx or G-Wan can be used. Potentially you can be talking 200kB rather than 200MB depending on OS, httpd and PHP setup, 6x less memory under high load, and 2x more requests/second just from this factor alone. Look here:
http://nbonvin.wordpress.com/2011/03/24/...er-to-use/
4. Faster pages = higher Google pagerank, happier viewers. Every millisecond counts (for some websites).
5. Avoiding PHP/apache means much less memory usage - cheaper VPS/Amazon costs. Or, it means you can cache absolutely everything in physical RAM for ultra-fast speeds, vs hitting the disk filesystem or virtual memory on your VPS slice.
6. Continually watching out for security updates is a drain on my 'attention' as a sysadmin. I'd rather avoid it.
7. Just for fun: http://www.amazon.com/dp/0596529309/?tag...verfl08-20
Also check out http://load-impact.com - lets you stress test your site.
Example here: http://www.webandblog.com/reviews/apache...eavy-load/
