I have added memcache as an option to the core of Hotaru CMS and am looking for a few sites that want to test it. If successful this will be standard in the v.1.6.0 Hotaru CMS version which is planned for release by the end of this month. Currently I have memcache running on http://ipadrank.com in debug mode and am displaying the stats at the botom of the page. I have added a counter showing the number of cached queries in addition to the db queries. I have set my cache memory to be only 20 seconds here so that you can see the query numbers changing. At the moment I have set up memcache to do the following: When Hotaru CMS goes to read from the db it first checks in memcache for the query. If the query already exists and is not more than 20 seconds old, then the results data from the query is shown instead of querying the db If the query does not exist then Hotaru CMS calls the db and saves it to memcache as well as returning the data for the user to see If this test is successful and people are interested the next step would be : When inserting a new record, to save the query and data to memcache as well as saving to db. This means that the next time Hotaru CMS looks for the data on a SELECT call to the db it will already be in memcache. This will also mean that data gets updated in memcache without waiting for the 20 seconds to expire before the db gets a fresh call. This can apply to INSERT, UPDATE, DELETE and any other commands The advantage of this second step comes if you set the memcache expiry to say 10 minutes or something large. That way the data should always be uptodate without having to make the user refresh a large amount of records I have modified the mysqli driver version of ezsql to do this and so at the moment it will not work with the mysql driver version. Note: there are 2 drivers we support for the mysql database. They are called mysql and mysqli. It is confusing to have the same name for driver and database, but if you are unsure turn debug mode on and look in the footer to see what your driver is. No changes are required to the database to use memcache but you need to have memcache installed on your server. If you are unsure let me know When we move this into the release for v.1.6.0 we will have to consider how to turn memcache on and off in the admin panel and how to balance it against the current db_cache which is file based. Since queries will be saved to memory with memcache there will be no point in also saving those same queries to disk. When testing you will need to turn off db_cache. Things seem to be working well on ipadrank with memcache but I want to get an idea of how it works with different servers and whether people actually feel a different in page speed. Compared to popular CMS systems like Wordpress which typically can require 500 - 1,000 database queries to construct a page, Hotaru CMS only has about 50 - 100 queries. This is quite a small amount for CMS's and already produces a fast page load. I am keen to see whether memcache actually makes a big difference or not. Who is interested to try it out?