Comments on: Application scaling and memcache http://blog.projectxtech.com/2007/09/17/application-scaling-and-memcache/ Start-ups, Maps and Local Search in New Zealand Thu, 28 Aug 2008 04:09:52 +0000 http://wordpress.org/?v=2.6 By: David Preece http://blog.projectxtech.com/2007/09/17/application-scaling-and-memcache/#comment-932 David Preece Mon, 17 Sep 2007 23:09:27 +0000 http://blog.projectxtech.com/2007/09/17/application-scaling-and-memcache/#comment-932 Django also recently sprouted a built in way to store session data in memcache instead of hitting the database even harder (http://code.djangoproject.com/changeset/6333). It appears to be merely a case of putting "SESSION_ENGINE=django.contrib.sessions.backends.cache" in settings.py. And setting up memcache, obviously. Django also recently sprouted a built in way to store session data in memcache instead of hitting the database even harder (http://code.djangoproject.com/changeset/6333). It appears to be merely a case of putting “SESSION_ENGINE=django.contrib.sessions.backends.cache” in settings.py. And setting up memcache, obviously.

]]> By: Stephen Judd http://blog.projectxtech.com/2007/09/17/application-scaling-and-memcache/#comment-928 Stephen Judd Mon, 17 Sep 2007 04:30:13 +0000 http://blog.projectxtech.com/2007/09/17/application-scaling-and-memcache/#comment-928 You may find this interesting, if you haven't read it already: http://koziarski.net/archives/2007/5/28/clever-caching . Get your keys right and the rest follows. My first instinct is to cache from the user end back. The less deep into the stack the request has to go, the better. You may find this interesting, if you haven’t read it already: http://koziarski.net/archives/2007/5/28/clever-caching . Get your keys right and the rest follows.

My first instinct is to cache from the user end back. The less deep into the stack the request has to go, the better.

]]>