FWIW we used Memcached for session data at Digg without any major issues. The one thing we did end up doing to reduce the LRU on sessions was to modify the slab size and put sessions in their own Memcached cluster. Probably not an issue for you though.
+1 on Memcached. On Feb 1, 2011, at 9:57 AM, buddhasystem wrote: > > For completeness: > > http://stackoverflow.com/questions/3746685/running-django-site-in-multiserver-environment-how-to-handle-sessions > http://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cached-sessions > > I guess your approach does make sense, one only wishes that the servlet in > question did more work for you. If I read correctly, Django can cache > sessions transparently in memcached. So memcached mecomes your Session > Management System. Is it better or worse than Cassandra? My feeling is that > it's probably faster and easier to set up. > > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/cassandra-as-session-store-tp5981871p5982024.html > Sent from the [email protected] mailing list archive at > Nabble.com.
