On 04/04/2012 10:31, William A. Rowe Jr. wrote: > On 4/3/2012 9:50 PM, Jim Schueler wrote: >> Hope this doesn't get trapped by too many spam filters. >> >> Sad news. Just saw a blog >> >> http://www.highscalability.com/ >> >> that reports YouPorn.com switched from Perl to PHP. Apparently there's a >> reported 10% >> improvement in speed, but I haven't noticed :). >> >> After a couple months of total immersion, I have less inclination towards >> PHP than ever. Fight's not out of me yet. > If one is comparing an every-connection mod_perl enabled environment > to a specific-content, fastcgi-proxied php buildout, there's no contest. > > When was the last time you built perl with no threading support? It's > certainly a 5%-15% win. Agreed. Honestly, I love mod_perl for easy Apache internals and for doing really cool things with the httpd API but if I was given a blank R&D department and told to build a web site (a public-facing HTML-based beast, not a webservice or some other API endpoint), I'd very likely pick PHP. It's faster and simpler (not easier, but simpler) for people to work with and if set up properly can be fast enough to serve. Since PHP's APC stabilized, I've always considered it to be "good enough" against the speed advantage of registry scripts....
Issac
