24.1.4. Caching PHP-Nuke: Conclusion

We have seen three approaches to PHP-Nuke acceleration in the previous sections:

• jpcache (see Section 24.1.1) can cache and compress a whole page - on disk.

• Cache-Lite (see Section 24.1.2) can cache and compress a whole page or individual PHP-Nuke blocks, modules, variables - on disk (or shared memory too? FIXME: someone please correct me here!).

• Turck MMCache (see Section 24.1.3) can cache and compress all of the above, plus can do encoding - all in shared memory!

So which tool is the right one for you?

There are a lot of combinations one could try there and without serious testing it is not easy to answer this question definitely. However, from what we have seen already in the previous posts, we can derive some strategies (see also How to accelerate PHP-Nuke):

• If you don't have administration access to your web server, you are left with jpcache and Cache-Lite. Use a combination of them as outlined above, caching whole pages with jpcache and individual blocks/modules with Cache-Lite. It's a strategic decision when to use which one - one you will have to make yourself.

• If you do have administration access to your web server, MMCache is the way to go. You can use it to cache PHP code and - optionally - a whole page content or just part of it. Whether you should prefer Cache-Lite for the latter, or decide to use MMCache, is something that probably only tests can show.

• Ease of deployment can also play a role: with MMCache, you add a line, with Cache-Lite a whole block of lines, to each PHP-Nuke module or block you wish to cache. On the other hand, Cache-Lite may live up to its name and prove itself to be really lightweight in some (or all) situations. Again, you wll have to test.