Code

Ticket #9986: cull_frequency.diff

File cull_frequency.diff, 1.1 KB (added by kgrandis, 5 years ago)

patch that does the opposite of ticket and replaces cull_percentage with cull_frequency

Line 
1Index: docs/topics/cache.txt
2===================================================================
3--- docs/topics/cache.txt       (revision 10177)
4+++ docs/topics/cache.txt       (working copy)
5@@ -234,12 +234,12 @@
6       backends, the maximum number of entries allowed in the cache before old
7       values are deleted. This argument defaults to 300.
8 
9-    * ``cull_percentage``: The percentage of entries that are culled when
10-      ``max_entries`` is reached. The actual ratio is ``1/cull_percentage``, so
11-      set ``cull_percentage=2`` to cull half of the entries when ``max_entries``
12+    * ``cull_frequency``: The fraction of entries that are culled when
13+      ``max_entries`` is reached. The actual ratio is ``1/cull_frequency``, so
14+      set ``cull_frequency=2`` to cull half of the entries when ``max_entries``
15       is reached.
16 
17-      A value of ``0`` for ``cull_percentage`` means that the entire cache will
18+      A value of ``0`` for ``cull_frequency`` means that the entire cache will
19       be dumped when ``max_entries`` is reached. This makes culling *much*
20       faster at the expense of more cache misses.
21