On Sat, Jun 18, 2016 at 9:53 PM, Richard Hipp <d...@sqlite.org> wrote:
> Performance problems come about more due to the number of files in a > single check-out. Most projects have a few thousand source files, for > which Fossil works great. When the number of files in a single > revision gets into the hundreds of thousands, then some operations can > become sluggish. > Also, the diff/merge bits need an amount of memory proportional to, but greater than, a file's size (potentially 2-3x), so storing very large files (e.g. CD images or huge multimedia blobs) may cause out-of-memory conditions on machines with limited memory/swap space. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
