On Wed, Mar 18, 2009 at 6:19 AM, hotani <[email protected]> wrote: > > The result? No difference. Memcached does not provide any benefit > according to my testing. I have siege set to log in as a user, then > hit a single page which makes several db calls. The memcached server > shows no movement in CPU, memory, or network usage which makes me > wonder if I even have things set up correctly at all.
Have you actually done anything in your application to utilize caching? Memcached isn't some sort of fairy dust that you turn on and your application magically becomes faster - you need to utilize the cache throughout your application. You mention that you have changed the cache backend, but you haven't mentioned what you have done in your application to make it use the cache. There are lots more details on what you can do here: http://docs.djangoproject.com/en/dev/topics/cache/ > Is there a way to check memcached to see if it is functioning > correctly? I tried entering a bogus ip in the CACHE_BACKEND setting in > settings.py and nothing changed. Django restarted normally with no > errors. To check if the cache is working at all, use the low-level cache API. Launch a Python shell, and try to put a key-value pair into the cache, then check that you can retrieve the value. The docs for the low-level cache API should give you an idea of what to run. http://docs.djangoproject.com/en/dev/topics/cache/#the-low-level-cache-api Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
