Charles, In my particular case it was primarily CPU bound as you can see from the time info. The CPU was between 95-100% busy the whole time. This is what concerned me. Having a backup program being IO bound would hardly be a surprise to anyone. Being CPU bound was somewhat of a surprise to me. Of course, for those of you with 3.2Ghz versus 1Ghz machines are likely no longer CPU bound.
Corey On 2/13/07, Charles Duffy <[EMAIL PROTECTED]> wrote:
[...] All that said, it would be interesting to do some benchmarking to see where time is actually being spent -- waiting for network latency, waiting for the filesystem or doing things in userspace. oprofile should easily distinguish between the latter two cases; more primitive tools (comparing wall-clock/user/system execution, for instance) should provide more general data on the former.
_______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
