On Tue, Jul 16, 2013 at 08:46:06AM -0400, Richard Hipp wrote: > On Tue, Jul 16, 2013 at 8:37 AM, Joerg Sonnenberger <jo...@britannica.bec.de > > wrote: > > > Hi all, > > in case someone has time to fix this, let me write up the most annoying > > performance issue for larger repositories. When running "fossil update", > > it will rewrite vfile table in .fslckout from scratch, even though most > > entries should not change on merges. If the working copy contains a few > > thousand files, that starts to take a very long time... > > > > Should that say "few hundred thousand" instead of "few thousand"?
Just a matter of scale :) Essentially, the problem is that t(fossil update) = O(files in the working copy), when it should be O(files changed). Joerg _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
