mirror of
https://git.proxmox.com/git/proxmox-backup
synced 2025-08-03 03:36:50 +00:00
docs: add description for gc-cache-capacity tuning parameter
Adds a bullet point to the listed datastore tuning parameters, describing its functionality, implications and typical values. Signed-off-by: Christian Ebner <c.ebner@proxmox.com> Link: https://lore.proxmox.com/pbs-devel/20250404130713.376630-4-c.ebner@proxmox.com [TL: address trivial merge conflict from context changes] Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
parent
6df6d3094c
commit
6c774660a7
@ -451,6 +451,13 @@ There are some tuning related options for the datastore that are more advanced:
|
||||
during phase 2 of garbage collection (given no older writers). If the
|
||||
``atime`` of the chunk is outside the range, it will be removed.
|
||||
|
||||
* ``gc-cache-capacity``: Datastore GC least recently used cache capacity:
|
||||
Allows to control the cache capacity used to keep track of chunks for which
|
||||
the access time has already been updated during phase 1 of garbage collection.
|
||||
This avoids multiple updates and increases GC runtime performance. Higher
|
||||
values can reduce GC runtime at the cost of increase memory usage, setting the
|
||||
value to 0 disables caching.
|
||||
|
||||
If you want to set multiple tuning options simultaneously, you can separate them
|
||||
with a comma, like this:
|
||||
|
||||
|
@ -301,7 +301,7 @@ Ext.define('PBS.Datastore.Options', {
|
||||
fieldLabel: gettext('GC cache capacity'),
|
||||
emptyText: Proxmox.Utils.defaultText,
|
||||
minValue: 0,
|
||||
maxValue: 8192 * 1024,
|
||||
maxValue: 8 * 1024 * 1024,
|
||||
deleteEmpty: true,
|
||||
step: 1024,
|
||||
},
|
||||
|
Loading…
Reference in New Issue
Block a user