Hello, I first want to say what a terrific version control manager Fossil is! I took my first serious look at Fossil last week and have already converted a few of my personal projects away from 'git'. The built-in bug tracker and wiki are genius touches! Thank you, Fossil community, for your efforts.
I would like to mention, however, that Fossil hits a scalability wall at some point, making it unsuitable for large projects. I have been trying to pull the NetBSD source repository for a week and have had nothing but problems. As of this moment, I haven't succeeded. I first tried cloning the repository, but it would exit with an error after ~2GB of data was transferred. I then downloaded the repository[2] from the NetBSD FTP site (>10GB !) Doing a 'rebuild' starts out fine but, after 24 hours, I get to 60% complete and then it take hours to advance another .1%. I tried to rebuild using various options (--wal and setting the pagesize), but it all ends up slowing down at the same place. The last time I tried it, the .fossil file was 10GB and the journal file reached 11GB! I was able to download and rebuild the pkgsrc repository[3] in a reasonable time -- it's only 2.7GB. So there's some point between the two projects in which fossil's rebuild algorithm becomes so expensive, it can't be cloned. I don't have any question; I just thought I'd document my experiences. -- Rich [1] http://netbsd.sonnenberger.org/ [2] http://ftp.netbsd.org/pub/NetBSD/misc/repositories/fossil/src.fossil [3] http://ftp.netbsd.org/pub/NetBSD/misc/repositories/fossil/pkgsrc.fossil _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
