From: Christian Ebner <c.ebner@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 4/4] docs: add description for gc-cache-capacity tuning parameter
Date: Fri, 4 Apr 2025 14:13:11 +0200 [thread overview]
Message-ID: <ab966abb-2108-436f-9a71-37072473623d@proxmox.com> (raw)
In-Reply-To: <17935971-dc70-4288-85d2-a7d125a61756@proxmox.com>
On 4/4/25 13:58, Lukas Wagner wrote:
>
>
> On 2025-04-03 14:27, Christian Ebner wrote:
>> 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>
>> ---
>> docs/storage.rst | 12 ++++++++++--
>> 1 file changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/docs/storage.rst b/docs/storage.rst
>> index 490302955..cab65ef79 100644
>> --- a/docs/storage.rst
>> +++ b/docs/storage.rst
>> @@ -435,9 +435,17 @@ There are some tuning related options for the datastore that are more advanced:
>>
>> This can be set with:
>>
>> -.. code-block:: console
>> + .. code-block:: console
>> +
>> + # proxmox-backup-manager datastore update <storename> --tuning 'sync-level=filesystem'
>>
>> - # proxmox-backup-manager datastore update <storename> --tuning 'sync-level=filesystem'
>> +* ``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. The
>> + capacity is set as the given value multiplied by 1024. Higher values can
>> + reduce GC runtime at the cost of increase memory usage, setting the value to 0
>> + disables caching.
>
> I think we could completely omit the "the capacity is set as the given value multiplied by 1024" sentence here
> and consider the fact that the LRU cache size is value * 1024 an implementation detail.
> For the user, the exact number of cached digests in the backend is probably not really that important, right?
Agreed, I opted for including this as the option states "capacity", so
one might expect the exact capacity. But you are completely right that
this is mostly unimportant for the end user.
> In reality, they just want some knob that they can adjust in a range from 0 (no caching) to some maximum.
>
> Same of course applies also for the GUI patch and the log message.
>
> What do you think?
Will send a new version which drops the mentions of multiples of 1024,
thanks for review and testing!
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-04-04 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 12:27 [pbs-devel] [PATCH proxmox] pbs api types: add garbage collection cache capacity tuning option Christian Ebner
2025-04-03 12:27 ` [pbs-devel] [PATCH proxmox-backup 2/4] garbage collection: set phase1 LRU cache capacity by " Christian Ebner
2025-04-03 12:27 ` [pbs-devel] [PATCH proxmox-backup 3/4] ui: expose GC cache capacity in datastore tuning parameters Christian Ebner
2025-04-03 12:27 ` [pbs-devel] [PATCH proxmox-backup 4/4] docs: add description for gc-cache-capacity tuning parameter Christian Ebner
2025-04-04 11:58 ` Lukas Wagner
2025-04-04 12:13 ` Christian Ebner [this message]
2025-04-04 12:20 ` Thomas Lamprecht
2025-04-04 12:28 ` Lukas Wagner
2025-04-04 12:37 ` Christian Ebner
2025-04-04 11:59 ` [pbs-devel] [PATCH proxmox] pbs api types: add garbage collection cache capacity tuning option Lukas Wagner
2025-04-04 13:08 ` [pbs-devel] superseded: " Christian Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab966abb-2108-436f-9a71-37072473623d@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal