Comments on: Put Your PHP App on Steroids – Optimizing with APC Cache

By: Radek Havelka

Radek Havelka — Thu, 05 Mar 2009 13:58:07 +0000

Hi,
first of all, thank you for the sharing of this code and article.
Let me remind you, that codes as mentioned in the article are not 100% correct : in class definition you are using “fetch” and “store”, in following code you are using “get” and “set” methods, so if someone (like me ) blindly copies the code, it will not work Else, the method is great and the APC caching reduced my pure PHP server load by 50%, which is very significant number. Thanks again.
R.

By: PHP cache performance

PHP cache performance — Sun, 12 Oct 2008 19:57:26 +0000

I was about to have a whinge about the needless, habitual reaching for OOP techniques in the simplest code examples – and then I was going to harp on about how you are aiming for better performance, but that OOP approaches don’t generally lend themselves to such ends.. and then I decided to run some experiments based on your code (http://www.spiration.co.uk/post/1392/PHP performance test – functional, or OOP comparison). Now I have to retract all of the above, since your code appears to perform distinctly better than the procedural equivalent. That’s gotten me scratching my head now ..

By: IT-Republik-php

IT-Republik-php — Fri, 11 Apr 2008 09:44:40 +0000

Web-Apps auf Speed: Eine Einführung in Caching mit APC…

Wenn eine Webanwendung erst einmal populär wird, kann die Last schnell zum …

By: Ian

Ian — Fri, 11 Apr 2008 08:07:07 +0000

@Jilles

You’re right, but I didn’t want to try and wrap them up into one post since there’s a bit more to getting memcached going than a simple PECL extension… I did mention right at the closer of the article that I’d hopefully be getting around to working with mecached (I’m just cooking something else up first that should be pretty cool

By: Jilles

Jilles — Fri, 11 Apr 2008 07:08:21 +0000

This is a good article. One note though: for large systems you’d want a cache that is local to that machine (APC can do this for you), but also a cache that is centralized (ex. memcached). You’ll want this as the number of servers is growing, you will increase the cache misses (depending on the data and it’s access patterns).

By: Ian

Ian — Wed, 09 Apr 2008 01:44:40 +0000

Christian,

I actually missed a bit of my code in the examples… you have to parse the result set then everything’s hunky-dory. I’ve updated the samples appropriately (I’m just used to having the pre-parsed from a database abstraction layer)

By: Christian Decker

Christian Decker — Wed, 09 Apr 2008 01:21:18 +0000

Thanks Ian for responding so quickly. I’m still having a small problem with the above example code as it saves a resource descriptor in the cache. Is the apc_cache intelligent enough to extract the resultrows from the resource, or did I get something wrong with the serialization?

By: Ian

Ian — Mon, 07 Apr 2008 05:44:21 +0000

@Christian,

You can store anything that php can serialize in the cache… which is just about anything in php

Thanks for the comment!

By: Christian Decker

Christian Decker — Mon, 07 Apr 2008 01:54:57 +0000

Great article, I’m definitely adding APC capabilities into my Database abstraction layer from now on.
I was wondering wether I can store arbitrary datasets into the cache, for example some datastructures for complex routing calculations that I’d like not to repeat every time.