Closed Bug 1449156 Opened 6 years ago Closed 6 years ago

Bugzilla::Memcached should use smaller timeouts and ping servers at instantiation time

Categories

(bugzilla.mozilla.org :: General, enhancement)

Production
enhancement
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: dylan, Assigned: dylan)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

45 bytes, text/x-github-pull-request
Details | Review
Cache::Memcached::Fast has the following features:

connect_timeout, default 0.7 seconds, the time that it takes to figure out a connection isn't working. (usually not encountered, as you get a NAK immediately, but not in AWS)

io_timeout, default 1 second, the time time that it takes before an io operation (get/set) times out.

failure_timeout, default 60 (but not used): the time to wait between failures

max_failures, default 0 (off): how many failures before we stop trying to connect?

I think 0.2 is a good value for the first two, and I really like the second one!
I think after 1 failure we should wait 60 seconds before hitting memcached again.
Attached file PR
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Get/Set operations when memcached is not present before this fix:
It can do 3 per second.

Get/Set operations when memcached is not present after this fix:
It can do 376970 sets per second
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: