#35166: Return python-memcached support
-------------------------------------+-------------------------------------
Reporter: Matej Spiller Muys | Owner: nobody
Type: New feature | Status: new
Component: Uncategorized | Version: 5.0
Severity: Normal | Resolution:
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
-------------------------------------+-------------------------------------
Description changed by Matej Spiller Muys:
Old description:
> In the past python-memcached was remove from Django (4.1).
> https://docs.djangoproject.com/en/5.0/releases/4.1/
>
> However https://github.com/linsomniac/python-memcached/releases was
> resurected with 3 released in past month solving both hacks needed in
> Django:
> https://github.com/linsomniac/python-memcached/issues/159
> https://github.com/linsomniac/python-memcached/issues/170
>
> Commit that deleted python-memcached:
> https://github.com/django/django/commit/05f3a6186efefc9fca2204a745b992501c6fd91f
>
> Why is python-memcached interesting today is because of HUUUGE
> performance degradation:
> https://github.com/pinterest/pymemcache/issues/478
>
> 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.
New description:
In the past python-memcached was removed from Django (4.1).
https://docs.djangoproject.com/en/5.0/releases/4.1/
However https://github.com/linsomniac/python-memcached/releases was
resurected with 3 released in past month solving both hacks needed in
Django:
https://github.com/linsomniac/python-memcached/issues/159
https://github.com/linsomniac/python-memcached/issues/170
Commit that deleted python-memcached:
https://github.com/django/django/commit/05f3a6186efefc9fca2204a745b992501c6fd91f
Why is python-memcached interesting today is because of HUUUGE performance
degradation:
https://github.com/pinterest/pymemcache/issues/478
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.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/35166#comment:1>
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/0107018d7982cfc1-458e9576-77aa-4ed0-a36e-eca0b75d18bd-000000%40eu-central-1.amazonses.com.
