Claus Witt

While looking at a post about using memcache for a simple message queue, which by the way sounds very interesting in its own right. I once again found a link to the MemcacheDB project. They have made memcache persistent. It is some sort of and intermediate between regular memcached and a database. I can think of several scenarios where memcachedb would be useful. One that comes to mind is persistent storage of user- og and settings- objects in the system that I am currently working on, for Voicearchive.com.

For a while we have worked on making our website at work more responsive. We have a lot of visitors looking for voice over talents, and since we primarily do business across the web, mainly through our website, it is important to us that it is as responsive as possible. Apart from the classic guidelines you always hear when running a website, we have experimented with a hacked version of Typo3 to enable the use of Memcached as a page cache.

And as I suspected, performance was highly impacted by this. Through all our optimizations we have reduced the load time of the page to an absolut minimal. Next we will look at ways to reduce the amount of javascript needed for some of our features.