Closed Bug 1181587 Opened 9 years ago Closed 9 years ago

Update python-memcached to v1.53

Categories

(Tree Management :: Treeherder, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

python-memcached (Current: 1.48 Latest: 1.54 [wheel])
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/27fed6557f190e2c3fd2a28dbdf5fd5719a7cb30
Revert ea0fbedf17 ("Bug 1181587 - Update python-memcached to v1.54")

To confirm whether this caused a response time regression for memcached
gets and sets.
Summary: Update python-memcached to v1.54 → Update python-memcached to v1.53
Numbers are stage get response times...

v1.53: ~3.8ms
e346892: ~3.9ms (changes: https://github.com/linsomniac/python-memcached/compare/release-1.53...e346892)
e268a8b: ~5.2ms (changes: https://github.com/linsomniac/python-memcached/compare/e346892...e268a8b)
918e88c: ~13ms (changes: https://github.com/linsomniac/python-memcached/compare/e268a8b...918e88c)

So looks like several of the Python 3 compatibility fixes regressed performance (at least on Python 2.7.8), but in particular:
https://github.com/linsomniac/python-memcached/commit/45403325e0249ff0f61d6ae449a7daeeb7e852e5

We can stay on 1.53 for now until it's resolved.

I'd also like to look at how pylibmc compares too, since we're already using it on Heroku.
fwiw updating from 1.48 to 1.53 improved perf for gets by about 20% \o/
You need to log in before you can comment on or make changes to this bug.