From: Roland <devzero@web.de>
To: Mark Schouten <mark@tuxis.nl>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Slow overview of existing backups
Date: Fri, 10 Mar 2023 11:02:58 +0100 [thread overview]
Message-ID: <70ec07ec-9ea9-570a-c9a8-07c88f373bf8@web.de> (raw)
In-Reply-To: <em8bb6ced8-f187-46ba-bbbf-e4281f1239a7@7e876ad7.com>
hello,
yes, this is really slow, i even observed timeouts (backup list simply
won't appear without any notice) when querying pbs while another node is
running a backup
> I have the feeling that when you request an overview now, all
individual backups are checked, which seems suboptimal.
yes, but did you know that zfs metadata caching sucks and this may also
be one reason for slowness?
see https://github.com/openzfs/zfs/issues/12028
there is improvement on the way:
https://github.com/openzfs/zfs/pull/14359
regards
roland
Am 25.01.23 um 11:26 schrieb Mark Schouten:
> Hi,
>
> Requesting the available backups from a PBS takes quite a long time.
> Are there any plans to start implementing caching or an overal
> index-file for a datastore? PBS knows when something changed in terms
> of backups, and thus when it’s time to update that index.
>
> I have the feeling that when you request an overview now, all
> individual backups are checked, which seems suboptimal.
>
> Thanks,
>
> —
> Mark Schouten, CTO
> Tuxis B.V.
> mark@tuxis.nl / +31 318 200208
>
>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2023-03-10 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 10:26 Mark Schouten
2023-01-25 16:08 ` Thomas Lamprecht
2023-01-26 8:03 ` Mark Schouten
2023-03-10 9:09 ` Mark Schouten
2023-03-10 10:16 ` Roland
2023-03-10 10:52 ` Mark Schouten
2023-03-13 12:48 ` Mark Schouten
2023-03-10 10:02 ` Roland [this message]
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=70ec07ec-9ea9-570a-c9a8-07c88f373bf8@web.de \
--to=devzero@web.de \
--cc=mark@tuxis.nl \
--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