#35166: Return python-memcached support
-------------------------------------+-------------------------------------
Reporter: Matej Spiller Muys | Owner: nobody
Type: New feature | Status: closed
Component: Core (Cache system) | Version: 5.0
Severity: Normal | Resolution: wontfix
Keywords: memcached | Triage Stage:
performance get_many | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Matej Spiller Muys):
The architecture of pymemcache is not allowing such flow without major
refactoring since they splited multi server logic into separated logic
making it hard to fix it.
That's why the issue was not solved and does not look to be solved in the
near future unfourtanetly. I tried refactoring of pymemcache but it is
really hard and would take considerable amount of development.
I understand you cannot add/remove memcached libraries every 2 releases
but still current implementation of pymemcache is multiple times slower
when using multiple servers. It's was a huge regression in Django memcache
(we use 4 server so 4x times slower multi_get).
The interface of python-memcached interface is now aligned with pymemcache
so no longer need for hacks.
--
Ticket URL: <https://code.djangoproject.com/ticket/35166#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d79c82ad3-294f909e-20be-4994-989a-902a8b3cd44a-000000%40eu-central-1.amazonses.com.
