From 5f26349326655e37767adf4acb7963c8a7fc2695 Mon Sep 17 00:00:00 2001 From: ben Date: Fri, 19 Jul 2002 06:44:03 +0000 Subject: Added FAQ question on speed. git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@168 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109 --- rdiff-backup/FAQ-body.html | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/rdiff-backup/FAQ-body.html b/rdiff-backup/FAQ-body.html index 00962b8..9d1c64f 100644 --- a/rdiff-backup/FAQ-body.html +++ b/rdiff-backup/FAQ-body.html @@ -14,6 +14,9 @@ syntax". What's happening?
  • Does rdiff-backup work under Solaris?
    • +
  • How fast is rdiff-backup? Can it be run on large +data sets?
    • +

    Questions and Answers

    @@ -202,4 +205,25 @@ at least I think I've now got round it). +

    + +

  • How fast is rdiff-backup? Can it be run on large +data sets? + +

    rdiff-backup can be limited by the CPU, disk IO, or available +bandwidth, and the length of a session can be affected by the amount +of data, how much the data changed, and how many files are present. +That said, in the typical case the number/size of changed files is +relatively small compared to that of unchanged files, and rdiff-backup +is often either CPU or bandwidth bound, and takes time proportional to +the total number of files. Initial mirrorings will usually be +bandwidth or disk bound, and will take much longer than subsequent +updates. + +

    To give two arbitrary data points, when I back up my personal HD +locally (about 9GB, 600000 files, maybe 50 MB turnover, 1.1Ghz athlon) +rdiff-backup takes about 35 minutes and is usually CPU bound. Another +user reports an rdiff-backup session takes about 3 hours (80GB, ~1mil +files, 2GB turnover) to back up remotely Tru64 -> linux. + -- cgit v1.2.1