php|architect magazine has released their latest issue - the August 2007 edition. The cover story for this month is a piece by Dirk Merkel covering the automation and benchmarking/code profiling of your application to find potential issues before your customers/users do.

Other great articles in this issue include:

• a look at Flex and the Zend Framework
• part one of a series on normalization (Chinese)
• using cURL to extract pages and their data
• "The Job Interview" - an insiders guide.

There's two ways to get this issue - you can either subscribe to the magazine for a year (the PDF edition is only $40 USD) or you can buy the single issue for about $5 USD.

Paul Jones has information in this new post on his blog with a how-to on doing some benchmarking inside of the Solar application framework.

Comparative benchmarking is tedious work. It's not hard to do, it's just no fun to set up the same scaffold every time you want to figure out how long it takes different pieces of code to execute.

To do a benchmark, essentially you need only four things: a timing mechanism, a loop to run the first case, a loop to run the second case, and a way to show the time taken by each loop.

To illustrate, he gives example code of a simple loop and the output of its timing results. But, since this is a boring example, he demonstrates something a bit more complex - something using Solar_Test_Bench and Solar_Test. The example of using these two components pits require_once and Solar's own loadClass against each other. He also includes another similar test, one comparing fopen and exploding the include path to check for a file's existence.

Jean-François Bustarret talks about a topic in his new post the entire PHP community could definitely benefit from - PHP accelerators.

In the article, he looks at what accelerators are, how they work, and some of the ones that are currently out there in the market:

• APC
• eAccelerator
• Zend Platform

With the ground rules established, he breaks out the analysis into a few different rounds/categories including: support/maintenance, the accelerator's actual performance (including the code they used) and the results he discovered (all graphed out), and, finally, how they handle file updates made to the system.

In the end, there just isn't one that's a clear winner. What it really boils down to is what kind of situation you're in - Zend's option is good if you can pay for everything, otherwise, you'd do well to go with eAccelerator.