The mtime/stat(2) stress is expensive because it's a order(n) operation, but better than any other validation (checksumming) method -- is git not subject to similar performance hits ? Does it have a diff't method to verify integrity, or does it punt on that front because of guarantees from elsewhere, or a different requirements ?
-bch On 1/8/15, Joerg Sonnenberger <jo...@britannica.bec.de> wrote: > On Thu, Jan 08, 2015 at 07:29:53PM +0100, Stephan Beal wrote: >> The number of files is the primary factor, if i'm not sorely mistaken. > > Correct, but not in the way you expect :) For day to day operation, the > most annoying part is "fossil update", which rewrites the mtime table > completely. If you have 50k files, that's a lot of IO, especially as > almost nothing changes. The stat(2) part is a necessary evil, but by > itself quite fast, especially on a SSD. > > Joerg > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
