I have noticed that fossil reads the entire database file (in 1024 byte
increments) several times during the commit process, even when
committing a single file locally with no remote server.
While this doesn't matter for small repos (<10 MB), my test repo at 40
MB is border line unusable even when run from a fast solid state disk.
The physical directory structure has 5000 files totaling 270MB, but I
don't see any evidence of that being read by the fossil.exe process,
except for the particular file being checked in.
Is this behavior by design?
Mike
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users