0372c7ef04
The ETA restic displays was based on a rate computed across the entire backup operation. Often restic can progress at uneven rates. In the worst case, restic progresses over most of the backup at a very high rate and then finds new data to back up. The displayed ETA is then unrealistic and never adapts. Restic now estimates the transfer rate based on a sliding window, with the goal of adapting to observed changes in rate. To avoid wild changes in the estimate, several heuristics are used to keep the sliding window wide enough to be relatively stable.
17 lines
845 B
Text
17 lines
845 B
Text
# The first line must start with Bugfix:, Enhancement: or Change:,
|
|
# including the colon. Use present use. Remove lines starting with '#'
|
|
# from this template.
|
|
Enhancement: Improve the ETA displayed during backup
|
|
|
|
# Describe the problem in the past tense, the new behavior in the present
|
|
# tense. Mention the affected commands, backends, operating systems, etc.
|
|
# Focus on user-facing behavior, not the implementation.
|
|
|
|
Restic's backup command displayed an ETA that did not adapt when the rate
|
|
of progress made during the backup changed during the course of the
|
|
backup. Restic now uses recent progress when computing the ETA. It is
|
|
important to realize that the estimate may still be wrong, because restic
|
|
cannot predict the future, but the hope is that the ETA will be more
|
|
accurate in most cases.
|
|
|
|
https://github.com/restic/restic/issues/3397
|