Dar architecture questions

Hi,

I have recently started using dar to backup a fairly large number of 
files (it's maildir stuff) which consists of approx 136G of data in 
~1.68 million files.  I must complement dar since it is one of the few 
programs I tried that could actually complete an initial backup in a 
fairly reasonable period of time...it took just under 10 hours.

I have just started testing making a differential backup using the 
catalog from the full backup that was generated on the fly.  It works 
quite well but I do have some questions:

1) It takes 46 minutes if I am generating an on-the-fly catalog and 30 
minutes if not.  I haven't looked through the source yet, but I'm 
curious why there would be such a difference since it appears the 
catalog is kept in memory.

2) On both test runs I made the stats were displayed after ~21 minutes 
and the .dar slice does not appear to grow or be modified after this 
time.  What is dar doing during this period?

I included the stats display and the time for each run below.  This is 
dar v 2.4.8.

Thanks for a great software!

Kevin


diff with on-the-fly catalog 1.95GB mem usage
display of stats after 21 minutes
  --------------------------------------------
  12989 inode(s) saved
    including 6694 hard link(s) treated
  0 inode(s) changed at the moment of the backup and could not be saved 
properly
  0 byte(s) have been wasted in the archive to resave changing files
  1667844 inode(s) not saved (no inode/file change)
  0 inode(s) failed to be saved (filesystem error)
  2 inode(s) ignored (excluded by filters)
  3238 inode(s) recorded as deleted from reference backup
  --------------------------------------------
  Total number of inode(s) considered: 1684073
  --------------------------------------------

real	46m9.691s
user	44m30.220s
sys	0m57.140s


diff without on-the-fly-catalog 1.95GB mem usage
display of stats after 22 minutes
  --------------------------------------------
  13825 inode(s) saved
    including 6695 hard link(s) treated
  1 inode(s) changed at the moment of the backup and could not be saved 
properly
  0 byte(s) have been wasted in the archive to resave changing files
  1667221 inode(s) not saved (no inode/file change)
  0 inode(s) failed to be saved (filesystem error)
  2 inode(s) ignored (excluded by filters)
  3529 inode(s) recorded as deleted from reference backup
  --------------------------------------------
  Total number of inode(s) considered: 1684578
  --------------------------------------------

real	30m22.624s
user	29m30.580s
sys	0m45.270s

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev