Comments on: PHP Gets Boost with Facebook’s HipHop http://blog.utest.com/php-gets-boost-with-facebooks-hiphop/2010/02/ Software Testing Community Wed, 08 Feb 2012 08:18:02 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Stanton Champion http://blog.utest.com/php-gets-boost-with-facebooks-hiphop/2010/02/comment-page-1/#comment-14812 Stanton Champion Thu, 04 Feb 2010 16:15:58 +0000 http://blog.utest.com/?p=3579#comment-14812 Bradley, All three of those are excellent points. Thanks! Bradley,

All three of those are excellent points. Thanks!

]]> By: Bradley Holt http://blog.utest.com/php-gets-boost-with-facebooks-hiphop/2010/02/comment-page-1/#comment-14811 Bradley Holt Thu, 04 Feb 2010 16:14:29 +0000 http://blog.utest.com/?p=3579#comment-14811 This is really a great tool that Facebook has built and kudos to them for releasing it to the world under an free/open source license. It's worth noting that the vast majority of those deploying PHP applications will either a) not be able to use HipHop and/or b) not get any benefit out of using HipHop. There are many reasons for this and others have written some excellent blog posts on the topic, but I'll mention a few of the reasons here: 1. HipHop won't work on shared hosting environments which is where many PHP applications are deployed. 2. The bottleneck in most PHP applications is not PHP itself. Database access, for example, is usually a much bigger bottleneck. At Facebook's scale it makes sense to take performance improvements wherever you can get them. 3. If you have only one web server then you don't gain very much by using HipHop. You can't buy half a web server so cutting your resource usage in half doesn't get you much. This is really a great tool that Facebook has built and kudos to them for releasing it to the world under an free/open source license. It’s worth noting that the vast majority of those deploying PHP applications will either a) not be able to use HipHop and/or b) not get any benefit out of using HipHop. There are many reasons for this and others have written some excellent blog posts on the topic, but I’ll mention a few of the reasons here:

1. HipHop won’t work on shared hosting environments which is where many PHP applications are deployed.

2. The bottleneck in most PHP applications is not PHP itself. Database access, for example, is usually a much bigger bottleneck. At Facebook’s scale it makes sense to take performance improvements wherever you can get them.

3. If you have only one web server then you don’t gain very much by using HipHop. You can’t buy half a web server so cutting your resource usage in half doesn’t get you much.

]]>