Browse Source

Lower the memcache_socket_timeout to one second

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
tags/1.37.0^0
Lance Bragstad 2 months ago
parent
commit
f67262f0e7

+ 1
- 1
oslo_cache/_opts.py View File

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

+ 9
- 0
releasenotes/notes/lower_socket_timeout-ff5680a6be23bdb2.yaml View File

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

Loading…
Cancel
Save