public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Gabriel Goller <g.goller@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] datastore: avoid calculating protected attribute twice
Date: Thu, 4 Jul 2024 12:42:47 +0200	[thread overview]
Message-ID: <29ade279-d013-4d86-a663-23591e0a1800@proxmox.com> (raw)
In-Reply-To: <20240703150249.461110-1-g.goller@proxmox.com>

nit: s/calculating/checking/ as this is not really a calculation in that 
sense. But this does not warrant a new version.

On 7/3/24 17:02, Gabriel Goller wrote:
> The protected status of the snapshot is retrieved twice. This is slow
> because it stat's the .protected file multiple times.
> 
> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> ---
>   src/api2/admin/datastore.rs | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/src/api2/admin/datastore.rs b/src/api2/admin/datastore.rs
> index f28fb97fa975..9c5ef7185b74 100644
> --- a/src/api2/admin/datastore.rs
> +++ b/src/api2/admin/datastore.rs
> @@ -505,7 +505,7 @@ fn list_snapshots_blocking(
>               group: group.into(),
>               time: info.backup_dir.backup_time(),
>           };
> -        let protected = info.backup_dir.is_protected();
> +        let protected = info.protected;
>   
>           match get_all_snapshot_files(&info) {
>               Ok((manifest, files)) => {

This looks good to me, although there is now a possibly increased delay 
between the check and closure invocation, as the closure call can be 
significantly later, e.g. when there are a lot of snapshots in the group 
to list. This is however not problematic, as callers do not rely on this 
and the avoided lookup for the file path existence is beneficial.

Did test this by setting a snapshot to protected and verifying the 
listing is still as expected via:

```
proxmox-backup-client snapshot list <group> --output-format json-pretty
```

So please consider:

Tested-by: Christian Ebner <c.ebner@proxmox.com>
Reviewed-by: Christian Ebner <c.ebner@proxmox.com>


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


  reply	other threads:[~2024-07-04 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 15:02 Gabriel Goller
2024-07-04 10:42 ` Christian Ebner [this message]
2024-07-12 12:01 ` [pbs-devel] applied: " Wolfgang Bumiller

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=29ade279-d013-4d86-a663-23591e0a1800@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=g.goller@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