Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Artur Graniszewski's Blog:
Drupal 7: HipHop for PHP vs APC - benchmark
May 19, 2011 @ 16:01:20

Artur Graniszewski has written up a comparison of the performance of a standard Durpal 7 installation using HipHop versus APC to handle the optimization of the application.

There have been many suggestions on improving Drupal performance, some of them recommend the use of APC module, data caching, or even compilation of the entire system through HipHop for PHP. While the first two solutions have been successfully implemented, no one was able to perform the build process. After many battles with the the compiler and the Drupal code, I present you results of the first successful translation of Drupal 7 to C++ language

He introduces the methods he used and the statistics of the platform (hardware) he tested with. He also includes the software used and compile commands used to create the compiled Drupal version. Included in the post are graphs showing CPU usage comparing the two types of testing (HipHop and APC) versus a normal PHP-based installation. It also briefly touches on concurrency levels and the different optimizations that could be made with the gcc compiler.

tagged: drupal apc hiphop benchmark cpu usage

Link:

Sebastian Bergmann's Blog:
Flickr: The Real World PHP 5 Benchmark
Mar 27, 2009 @ 17:03:08

Sebastian Bergmann has posted a real world benchmark as justification for moving from a PHP 4 to PHP 5 environment - evidence from Flickr's change.

Benchmarks such as the PHP / GCC / ICC Benchmark I posted quite a while ago on this blog are synthetic. They test "raw bytecode execution" speed that cannot be translated into real-world situations per se. Flickr recently migrated from PHP 4 to PHP 5. And here are their real world numbers.

The graph shows a dramatic drop in processing needed (CPU usage) at the moment they made the switch over from PHP4 to PHP5.The system processing usage stayed about the same (system processes like logging and memory handling) but the user CPU usage (like what the web server would use) saw an immediate change by almost twenty percent.

tagged: php5 php4 benchmark flickr cpu usage compare graph

Link:

Scott MacVicar' Blog:
Stupid Bug Reports
Feb 02, 2009 @ 15:34:18

Most of the bugs that get reported to the PHP project are pretty useful. They help developers track down those small, random issues that might slip through the cracks otherwise. There are, however, some of them that make you wonder a bit about the person that submitted them Scott MacVicar takes a look at a few of them in a new blog post.

Recently the PHP project has been receiving an increasing number of rather silly reports, these vary from simply not reading the manual, searching the internet or a fundamental lack of understanding how the internet works.

He points out three in particular (from the same person, no less) about things that shown an almost complete lack of understand of what PHP does. One was a request to make PHP use less CPU and another asking to make PHP censorship free and, finally, a request to make PHP more secure...by doing away with support for cookies.

Scott also suggests a few constructive things you can do before submitting a good (useful) bug report:

  • Gather together as much relevant information as you can (generalizations are bad)
  • Run performance checks against older PHP versions to try to pin down when the bug was added
  • And, finally: "don't get aggressive or be an asshole when your bug reports get closed".
tagged: stupid bug report bugphpnet censorship secure cookie cpu resources

Link:

Felix Geisendorfer's Blog:
PHP 5.2.1 was a evil release - check your server
Sep 27, 2007 @ 17:04:00

Felix Geisendorfer has a reminder from developers out there - "PHP 5.2.1 was an evil release":

While I was at php|works I heard a lot of people say how bad of a release 5.2.1 was and that I should stay away from it. Well I didn’t take it to seriously at this point, but when I checked what version of PHP we are running on my client project recently it turns out it was 5.2.1.

They were seeing performance issues (database related) so they upgraded to the latest version, 5.2.4, and immediately saw a performance jump of forty to sixty percent and a much lower amount of CPU usage. Upon some further research, he found a certain bug in 5.2.1 that could have been the culprit.

tagged: evil release performance issue cpu load bug upgrade evil release performance issue cpu load bug upgrade

Link:

Felix Geisendorfer's Blog:
PHP 5.2.1 was a evil release - check your server
Sep 27, 2007 @ 17:04:00

Felix Geisendorfer has a reminder from developers out there - "PHP 5.2.1 was an evil release":

While I was at php|works I heard a lot of people say how bad of a release 5.2.1 was and that I should stay away from it. Well I didn’t take it to seriously at this point, but when I checked what version of PHP we are running on my client project recently it turns out it was 5.2.1.

They were seeing performance issues (database related) so they upgraded to the latest version, 5.2.4, and immediately saw a performance jump of forty to sixty percent and a much lower amount of CPU usage. Upon some further research, he found a certain bug in 5.2.1 that could have been the culprit.

tagged: evil release performance issue cpu load bug upgrade evil release performance issue cpu load bug upgrade

Link:


Trending Topics: