Enable some time estimate for --progress option (or a new --progress-total) option.
- Dominant language
- Perl
- Stars
- 2.1k
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
As `btrbk diff` already delivers a super nice overview of the difference of a parent and child snapshot, one could also get a time estimate during a `btrbk run`. This could be done by extending the existing `--progress` option, or by introducing a `--progress-total`.
Choosing this option, for every newly created snapshot `btrbk diff` would be run before `btrfs send/receive` such that the pv command can get proper `-s` option for the progress update.
This way it is easier to estimate the total time left, especially in cases where the network bandwidth is the limiting factor.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the existing --progress handling in btrbk run and the btrbk diff behavior described in the issue. Investigate how btrfs send/receive invokes pv and how a total size could be supplied for each newly created snapshot. Done means an agreed implementation of --progress or --progress-total that reports a useful total-time estimate during transfers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100