memcache_pool is there to keep a limited number of thread-associated
connections open rather than a connection for every thread. If you
don't have a huge number of threads it doesn't offer anything.
Keystone is an example of a service where memcache_pool doesn't
improve things -- eventlet isn't supported anymore and more threads
is not useful due to GIL.
As such, keystone cache backend is changed to dogpile.cache.memcached.
See https://review.openstack.org/357407 for the oslo.cache help text
change.
Change-Id: I4452a8c4968073cdea4c0f384453a5a28519fa08
| ... | ... |
@@ -245,7 +245,7 @@ function configure_keystone {
|
| 245 | 245 |
|
| 246 | 246 |
# Enable caching |
| 247 | 247 |
iniset $KEYSTONE_CONF cache enabled "True" |
| 248 |
- iniset $KEYSTONE_CONF cache backend "oslo_cache.memcache_pool" |
|
| 248 |
+ iniset $KEYSTONE_CONF cache backend "dogpile.cache.memcached" |
|
| 249 | 249 |
iniset $KEYSTONE_CONF cache memcache_servers localhost:11211 |
| 250 | 250 |
|
| 251 | 251 |
# Do not cache the catalog backend due to https://bugs.launchpad.net/keystone/+bug/1537617 |