I am testing fossil with a repository where some of the source files
define a few very large tables. These tables do not change often, but
when they do most of their content is replaced with something completely
different from the previous version.
When changes to these files are committed, fossil takes a long time to
process the commit (a couple of minutes for a 20MB table, over 10min for
a 60MB table). It would be nice if fossil could handle these commits
much faster, but that in itself is not a big problem for us because the
tables rarely get changed. What is more problematic is that once a
change to the tables has been committed, cloning the repository also
takes a very long time. It seems the fossil clone command is attempting
to re-apply delta encoding to all files in the repository and that is
causing the slowdown. Is re-encoding necessary when performing a clone
operation? If it is not necessary, Is there a way to prevent fossil
from re-applying delta encoding when cloning?
--
Edgardo M. Cruz | edgardo.c...@genkey.com
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
