In a recent post to his blog Dhiraj Patra looks at the caching functionality that PEAR has to offer via the PEAR Cache package.

Caching is currently a hot topic in the PHP world. Because PHP produces dynamic web pages, scripts must be run and results must be calculated each time a web page is requested, regardless if the results are the same each time. In addition, PHP compiles the script every time it is requested. [...] PEAR's Cache package offers a framework for the caching of dynamic content, database queries, and PHP function calls.

He talks a bit about what kind of methods are included with the package and shows examples of how it works for function call caching, caching the output from the script execution and how to implement your own custom caching extension of the main code to make it even more flexible.

Doug Brown has posted a new entry to his blog about how the Zend_Cache component of the Zend Framework has saved him some money.

He and his site were taken offline by his own hosting company because of one little detail - the limit on usage for the shared server was 3% and his site was using 30%. Going through his logs, he found the culprit - a "too many connections" message from MySQL due to the number of requests.

I'll admit, I was in a huge hurry to get this project done, so I wasn't thinking about the long term effects. Needless to say, I wasn't caching my MySQL query results. I know, tisk tisk.

He added a new private method to his class (using Zend_Cache to store the date) and dropped the call into his controller to pulled the cached info whenever it needed it.

Brian Moon has announced the release of the latest version of his memproxy tool that uses memcache to create a "server" to save the proxy information.

I put server in quotes because it is really just a PHP script that handles the caching and talking to the application servers. Apache and other HTTP servers already do a good job talking HTTP to a vast myriad of clients. I did not see any reason to reinvent the wheel.

Features of this new version include a TTL for the cached data, minimal dependencies for the application to use and a small code base consisting of two files. It also handles HTTP 1.1 requests, is transparent and applows pages to dynamically be specifically added and removed from the cache.

You can download this latest version from the project's page on the Google Code website.

Brian Shire has posted a new tutorial talking about some of the benefits of caching the functionality of your website (with things like APC, not file or database caching):

Opcode caches save energy, expenses, improve overall user experience on web sites, and it's often one of the simplest optimizations to implement. This article will explain the basics of installing, configuring, and tuning an opcode cache for PHP, the Alternative PHP Cache (APC).

The article focuses on how the APC works and how to get it up and working on your installation (as pulled from the pecl repositories). They look at some of the functions the extension's API includes (like ap_cache_info or ap_store for manual caching) as well as some more advanced topics like locking performance, working with TTL, cache priming and filtering.

Andi Gutmans of Zend has posted about the next step in his personal growth on the internet - a personal site/blog of his own over at andigutmans.com.

For years I've wanted to run a personal Web site but never found the time to do it. A couple of weeks ago a few Zenders and I started leasing a dedicated server which gave us each a bit more hosting flexibility. Once we got the machine up and running I decided it was finally time to actually launch my own personal Web site.

He lists the technologies he's using including the Zend Framework, the Zend_Gdata component and the Zend_Cache (for local caching of his blog feeds from Blogger).

The New Earth Online has a quick look at one easy method for speeding up your site in a few different ways - caching pages and information with things like Cache_Lite and APC.

As your site traffic grows it takes longer and longer to generate a dynamic page from sending multiple queries to a database. One possible solution to limit queries is to cache the result of each query that is needed, or to have a complete full page cache for your site.

They look at the two ways I mentioned - the Cache_Lite PEAR package and the APC extension (that will soon be included by default in the stable PHP releases). Bits of code are provided for each showing how to get them set up and get them working inside of your application.

In this new post to his blog, Ian Selby talks about a method to "pump up" your web site's performance to give the most to your visitors - the APC cache.

Nothing's cooler than writing a bad-ass site or application and watching it gain popularity and a significant user base. By the same token, nothing's more frustrating that watching your app fall on its face when its running under high load. [...] Before you say, "throw more / better hardware at that mo-fo", why not take a moment and learn about APC: Alternative PHP Cache...

He describes the caching software - what it is and how it can help you and your application - and includes examples using a CacheManger class to store and set values quickly and easily.

Lukas Smith got a chance to catch up with Rasmus Lerdorf (and others in #php.pecl) and "talk shop" about topics including handling large libraries and maxclients settings.

In this first post I will provide a link and some commentary on Rasmus's points regarding Doctrine (note I left independent chatter in the log in order to not have any chance of me filtering the content, but there is very little of that so I hope the discussion is still easy enough to follow).

Mike Willbanks has posted an introduction he's written up giving some helpful hints at tuning your servers and PHP applications for performance.

The focus of this post is not to show performance related items to specific PHP frameworks since many bottlenecks actually apply before running the framework itself that should certainly be solved up front. Therefore in this posting I attempt to look at simple items that can be deployed in order to produce finer tuned systems.

He talks about a few different aspects:

• PHP Performance Tuning (opcode caching, apc file priming, includes, loops, etc)
• RDBMS Performance Tuning (indexes in queries, query caching, archiving)
• HTTP Performance Tuning (content compression, css sprites, limit modules, etc)

In a new blog post Richard Thomas takes a deeper look (well continues his ) at the performance of the Zend_Loader component of the Zend Framework.

When you use Zend_Loader your files are wrapped in conditional statements. These statements prevent APC and all other cache/accelerator programs to have problems properly caching your file. [...] Now here is the catch-22. Depending on the size of your application and how often different classes are used you can run into problems.

His result doesn't have much to do with the component, though - he points out that conditionals of any type can slow things down in an application and that "benchmarking is your friend".