From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] applied: [PATCH v3 proxmox-backup] partial fix #5560: client: periodically show backup progress
Date: Fri, 18 Oct 2024 09:53:42 +0200 [thread overview]
Message-ID: <e70d1ff4-3373-42c3-a014-16feb65a57dc@proxmox.com> (raw)
In-Reply-To: <65709388-789e-4531-acfa-38eefed6be78@proxmox.com>
Am 18/10/2024 um 09:37 schrieb Christian Ebner:
> One thing still came to mind yesterday though:
> Progress logging is now enabled unconditionally, and as is it is not
> possible to disable it or configure the interval.
>
> So I plan to send a patch to make the progress log output opt-in, and
Personally I'd prefer opt-out, I'm not a fan of tools that stay silent
by default (looking at you `dd`).
Tools can always turn this off easily, and we already have some output
so it's not like we'd previously have none and now suddenly print stuff,
which might indeed surprise some existing users that relied on no output
(IMO a bit weird thing to do, but well not completely out of the picture)
> make the interval configurable within a meaningful value range (maybe
> within 0s to 3600s?).
>
> Something like:
> ```
> proxmox-backup-client backup root.pxar:/ --progress-log-interval=10
> ```
>
> And disable progress log output for a value of 0 or the optional
> parameter is not given.
>
> That would also allow to more flexibly control the behavior when being
> invoked by vzdump.
>
> What are your opinions on that?
Minus the s/opt-in/opt-out/ preference that's fine by me. We could then
also switch to a higher reporting rate in PVE, albeit FWIW, for VM backups
there we use 10s and then slow down after some time, trying to take a
balance for early fast feedback and short backups and long backups.
And just throwing out ideas, one could also do a size-related interval,
like print a report every (at least) X MB or GB uploaded.
Oh, and do you plan to take a TimeSpan as interval parameter? Might
provide nice UX here.
_______________________________________________
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:[~2024-10-18 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 9:33 [pbs-devel] [PATCH v3 proxmox] time: drop trailing space when not showing seconds at end Christian Ebner
2024-10-11 9:33 ` [pbs-devel] [PATCH v3 proxmox-backup] partial fix #5560: client: periodically show backup progress Christian Ebner
2024-10-17 15:02 ` [pbs-devel] applied: " Thomas Lamprecht
2024-10-17 15:53 ` Christian Ebner
2024-10-18 7:20 ` Thomas Lamprecht
2024-10-18 7:37 ` Christian Ebner
2024-10-18 7:53 ` Thomas Lamprecht [this message]
2024-10-18 8:33 ` Christian Ebner
2024-10-18 12:13 ` Thomas Lamprecht
2024-10-17 13:16 ` [pbs-devel] applied: [PATCH v3 proxmox] time: drop trailing space when not showing seconds at end Thomas Lamprecht
2024-10-17 14:40 ` Christian Ebner
2024-10-18 12:12 ` Thomas Lamprecht
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=e70d1ff4-3373-42c3-a014-16feb65a57dc@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@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