#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: Nick Pope (added)
* resolution: => wontfix
* status: new => closed
* component: Uncategorized => Core (Cache system)
Comment:
Thanks for this ticket, however I don't think we would like to re-add
`python-memcached` support.
> Basically pymemcache get_many is very slow because it send the request
to first sever wait for response, then to second server waiting for
response.
> But python-memcached first sends the requests to all servers and then
waits for responses making it number of memcached servers times faster.
This should be fixed in `pymemcache`, we cannot add/remove `memcached`
libraries every 2 releases.
You can [https://docs.djangoproject.com/en/stable/internals/contributing
/triaging-tickets/#closing-tickets follow the triaging guidelines with
regards to wontfix tickets] and take this to DevelopersMailingList, if you
don't agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/35166#comment:3>
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/0107018d79ba54f8-a293dd0a-799a-4499-8908-40b076d9e79f-000000%40eu-central-1.amazonses.com.
