Running a instance at http://ask.stg.fedoraproject.org/questions/ with memcached and it seems buggy. If two people are logged in, I see in the frontpage as noone has logged in but if I go to the people page, I see the other person as logged in and if I go to the questions page, I see myself logged in. Something is buggy here but very fast compared to, without memcached.
Thanks but this is still buggy. If I ask a question, it doesn't show up and the old cached page is shown instead. Sometimes when I go to the questions page I get a page not found instead and I have to refresh. This is problematic.
Could you verify that in runserver? AFAIK without the caching middlewares at this point pages in askbot won't be cached. It is possible that previous cached responses set very far in in the future "Expires" headers. Try deleting cache in the browser - does it help?
Cleared the cache and that didn't fix the problem but I touched the wsgi file and seems to work fine now. Will test more but there seems to some issues here under the surface
If you have have 'django.middleware.cache.UpdateCacheMiddleware', and it's twin 'django.middleware.cache.FetchFromCacheMiddleware', in the MIDDLEWARE_CLASSES then please remove them.
The effect you see is due to caching whole pages - including the header part on top.
Even without the page caching now you will get benefit from your memcached instance - because site settings are cached heavily. Settings are used many times in the course generating output.
We are planning some work to improve support of caching, some things can be done very easily.
Comments