[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[rdiff-backup-users] What are the bottlenecks in --verify? (Or how to sp
[rdiff-backup-users] What are the bottlenecks in --verify? (Or how to speed up verification?)
Wed, 25 Sep 2013 23:12:41 -0400
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
What are some options for speeding up the verification of past increments?
My guess is that the CPU might be a bottleneck for the SHA1 hash
calculation, so that's something I would check first.
But how does the verify process work? Does it reconstruct the file in
memory, or does it use a temporary directory?
It seems like if I don't have TMP, TMPDIR, or TEMP defined as
environment variables, it is operating system dependent on where Python
creates the temporary file. Or unless I pass the --tempdir option to
And if the --verify or --verify-at-time options create lots of temporary
files, and write/read lots of data to the temporary directory, then I
should probably move that directory to a separate set of spindles.
|[Prev in Thread]
||[Next in Thread]|
- [rdiff-backup-users] What are the bottlenecks in --verify? (Or how to speed up verification?),
Thomas Harold <=