Opened 16 years ago
Closed 14 years ago
#8414 closed (fixed)
multiple sites on one memcached
Reported by: | urban | Owned by: | nobody |
---|---|---|---|
Component: | Core (Cache system) | Version: | 1.2 |
Severity: | Keywords: | cache prefix session cached_db | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | yes | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
For every site which use for example CacheMiddleware we need to run new memcached instance, its not efficient with few small sites. I think that adding a key_prefix to the CACHE_BACKEND params will solve this problem. I've attached patch aganist memcache backend.
Attachments (1)
Change History (7)
by , 16 years ago
Attachment: | cahche.patch added |
---|
comment:1 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 16 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
It solves some problems, but not all, cache can be also set in other (than the CacheMiddleware) aplications, so maybe reimplement it in the cache framework instead of only in CacheMiddleware?
comment:3 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
With only this informations the issue is invalid since it describes no bug or new feature.
Describe it clearer maybe with a testcase.
comment:5 by , 14 years ago
Keywords: | session cached_db added |
---|---|
Needs tests: | set |
Resolution: | invalid |
Status: | closed → reopened |
Version: | SVN → 1.2 |
Using cached_db backend for session sharing memcached with diferent django sites may create session_id conflicts in memcached, using CACHE_MIDDLEWARE_KEY_PREFIX in cache backend solve it.
comment:6 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
A site-wide cache prefix was added in [14623]
What about just using CACHE_MIDDLEWARE_KEY_PREFIX?
http://www.djangoproject.com/documentation/settings/#cache-middleware-key-prefix
http://www.djangoproject.com/documentation/cache/#the-per-site-cache
I understand that will exactly solve the issue so I'm closing the ticket.
If that's not the issue feel free to reopen and comment.