Using --link-dest= multiple times - performance?
Nico -telmich- Schottelius
nico-rsync at schottelius.org
Mon Aug 20 11:02:06 GMT 2007
I'm thinking about using rsync with multiple times --link-dest= specified in
Now I'm wondering about the performance and memory usage:
- How much more memory will rsync use for every --link-dest= parameter?
- How heavy do you expect it to influence performance with every
additional --link-dest= parameter?
In general I think that rsync could either
- use index_size memory for each --link-dest, doing full index of the
- or just do stat() for each file in the source in each directory
specified by --link-dest
As stats() in general are not that heavy I expect it not to cost much
additional time, but on the other hand, stat()ing 50k files will still
take some time.
I'm just interested in what your ideas / thoughts about that are. If
the cost of cpu/ram is not too much, I would like to make it the
standard in ccollect to --link-dest to all existing backups (which can
be quite many, depending on the configuration).
Think about Free and Open Source Software (FOSS).
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/rsync/attachments/20070820/c6f480e4/attachment.bin
More information about the rsync