high ram use during initial full-signatures download
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
this is duplicity 0.6.23-1 on Debian Wheezy (Python 2.7.6). Backup target is an OpenStack Swift cluster.
I ran a first full backup of about 60,000 files resulting in a ~100gig backup and a ~1gig full-signatures file.
I then reran the backup from another server that had the same file set, so obviously duplicity had to download the full-signatures file to the .cache
During that download, the ram usage of duplicity soars - in the end to roughly the size of the full-signatures file, which hints that perhaps duplicity is buffering the download entirely in ram. That's ~1gig of ram!
Duplicity doesn't seem to require that much ram during normal backup operation - only around 22mb, so it doesn't seem necessary that the full-signatures data is held in ram.
Changed in duplicity: | |
status: | Confirmed → Fix Committed |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
I can confirm that this bug is still present in duplicity 0.7.08. Are there any plans to fix this?