sbackup uses too much memory

Bug #568384 reported by David Huggins-Daines on 2010-04-22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Status tracked in Trunk
Jean-Peer Lorenz
sbackup (Ubuntu)
Nominated for Jaunty by ngoel

Bug Description

Binary package hint: sbackup

sbackupd is currently running an incremental backup, and has been for 4.5 hours. its resident memory usage is nearly 800M:

root 16734 6.7 19.8 904868 779996 ? SN 08:03 1:53 /usr/bin/python /usr/sbin/sbackupd

is it storing the entire set of files and properties in one big dictionary in memory?

ProblemType: Bug
Architecture: amd64
Date: Thu Apr 22 08:27:25 2010
DistroRelease: Ubuntu 9.10
Package: sbackup 0.10.5ubuntu2
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: sbackup
Uname: Linux 2.6.31-20-generic x86_64

David Huggins-Daines (dhuggins) wrote :
ngoel (nagendra-goel) wrote :

I notice the user who reported the issue, and that makes me suspect that the problem occurs if large databases and
large files need to be backed up (overall disk size in terabytes).

Jean-Peer Lorenz (peer.loz) wrote :

I confirm that there is room for improvement and I'm already working on something in trunk. Though, please don't ask for a release date and note this won't fix in any of the current stable series (0.10.x and 0.11.x as packaged in Lucid, Maverick, Natty).

summary: - sbackupd uses way too much memory
+ sbackup uses too much memory
Changed in sbackup (Ubuntu):
status: New → Confirmed
Changed in sbackup:
importance: Undecided → Wishlist
status: New → In Progress
assignee: nobody → Jean-Peer Lorenz (peer.loz)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers