diff options
| author | Tim Burke <tim.burke@gmail.com> | 2022-01-06 12:09:58 -0800 |
|---|---|---|
| committer | Matthew Oliver <matt@oliver.net.au> | 2022-08-30 18:49:48 +1000 |
| commit | 5c6407bf591121fa10f8a8b10d22b3a64b9c4fe9 (patch) | |
| tree | 5bbfae68d227452dfc88ee23b4ea1a7b1b0f0535 /etc | |
| parent | 24acc6e56b25a4c53fcbe451a3a7c3d71d8c5beb (diff) | |
| download | swift-5c6407bf591121fa10f8a8b10d22b3a64b9c4fe9.tar.gz | |
proxy: Add a chance to skip memcache for get_*_info calls
If you've got thousands of requests per second for objects in a single
container, you basically NEVER want that container's info to ever fall
out of memcache. If it *does*, all those clients are almost certainly
going to overload the container.
Avoid this by allowing some small fraction of requests to bypass and
refresh the cache, pushing out the TTL as long as there continue to be
requests to the container. The likelihood of skipping the cache is
configurable, similar to what we did for shard range sets.
Change-Id: If9249a42b30e2a2e7c4b0b91f947f24bf891b86f
Closes-Bug: #1883324
Diffstat (limited to 'etc')
| -rw-r--r-- | etc/proxy-server.conf-sample | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/etc/proxy-server.conf-sample b/etc/proxy-server.conf-sample index 44a456219..0c14d8072 100644 --- a/etc/proxy-server.conf-sample +++ b/etc/proxy-server.conf-sample @@ -153,8 +153,10 @@ use = egg:swift#proxy # data is present in memcache, we can periodically refresh the data in memcache # without causing a thundering herd. Values around 0.0 - 0.1 (i.e., one in # every thousand requests skips cache, or fewer) are recommended. +# container_existence_skip_cache_pct = 0.0 # container_updating_shard_ranges_skip_cache_pct = 0.0 # container_listing_shard_ranges_skip_cache_pct = 0.0 +# account_existence_skip_cache_pct = 0.0 # # object_chunk_size = 65536 # client_chunk_size = 65536 |