openstack/oslo.cache
Code Issues Proposed changes

Lower the memcache_socket_timeout to one second

Browse Source 
Lowering this setting still allows for reasonable confidence of a
timeout without tanking performance.

Certain downstream projects have already made this optimization:

  https://github.com/crowbar/crowbar-openstack/pull/1429

Change-Id: Iaca2f8cc09a6acae425c020a9d14da3ffde05dec
This commit is contained in:
Lance Bragstad 2019-07-22 14:57:52 +00:00
parent a5023ba275
commit f67262f0e7
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
oslo_cache/_opts.py
View File

@ -83,7 +83,7 @@ FILE_OPTIONS = {
' before it is tried again. (dogpile.cache.memcache and' ' before it is tried again. (dogpile.cache.memcache and'
' oslo_cache.memcache_pool backends only).'), ' oslo_cache.memcache_pool backends only).'),
cfg.FloatOpt('memcache_socket_timeout', cfg.FloatOpt('memcache_socket_timeout',
default=3.0, default=1.0,
help='Timeout in seconds for every call to a server.' help='Timeout in seconds for every call to a server.'
' (dogpile.cache.memcache and oslo_cache.memcache_pool' ' (dogpile.cache.memcache and oslo_cache.memcache_pool'
' backends only).'), ' backends only).'),

9
releasenotes/notes/lower_socket_timeout-ff5680a6be23bdb2.yaml Normal file
View File

@ -0,0 +1,9 @@
---
upgrade:
- |
The default value for ``memcache_socket_timeout`` has been lowered from 3
seconds to 1 second. The positive side-effect of this can be found in
downstream `changes
<https://github.com/crowbar/crowbar-openstack/pull/1429>`_. If you
deployment relies explicitly on a timeout of 3 seconds, please set that
override in your configuration.