Ticket #9986: cull_frequency.diff

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

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

  • docs/topics/cache.txt

     
    234234      backends, the maximum number of entries allowed in the cache before old
    235235      values are deleted. This argument defaults to 300.
    236236
    237     * ``cull_percentage``: The percentage of entries that are culled when
    238       ``max_entries`` is reached. The actual ratio is ``1/cull_percentage``, so
    239       set ``cull_percentage=2`` to cull half of the entries when ``max_entries``
     237    * ``cull_frequency``: The fraction of entries that are culled when
     238      ``max_entries`` is reached. The actual ratio is ``1/cull_frequency``, so
     239      set ``cull_frequency=2`` to cull half of the entries when ``max_entries``
    240240      is reached.
    241241
    242       A value of ``0`` for ``cull_percentage`` means that the entire cache will
     242      A value of ``0`` for ``cull_frequency`` means that the entire cache will
    243243      be dumped when ``max_entries`` is reached. This makes culling *much*
    244244      faster at the expense of more cache misses.
    245245
Back to Top