[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[rdiff-backup-users] Re: Restore stuck
|
From: |
Troels Arvin |
|
Subject: |
[rdiff-backup-users] Re: Restore stuck |
|
Date: |
Fri, 07 Apr 2006 09:40:38 +0200 |
|
User-agent: |
Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) |
On Sun, 12 Feb 2006 15:47:21 +0100, Troels Arvin wrote:
> On b, load avarage is high, and rdiff-backup has a resident set size of
> 356MB (rising). On r, load avarage is practically 0.
I tried using more potent hardware. It turned out that if I work on
servers with more RAM, thrashing doesn't occur, so the restore-process is
able to finish.
Involved in the restore are directories with ~30000 files. I suppose that
this is a hint about what's going on. Maybe rdiff-backup uses some
somewhat "expensive" python container structures which makes rdiff-backup
consume lots of RAM while restoring?
--
Greetings from Troels Arvin
- [rdiff-backup-users] Re: Restore stuck,
Troels Arvin <=