So, I had a fossil repo for a web app that has a lot of hands in it. I'm the only code developer (though not the first by many years--repo converted from CVS), but the application serves hundreds of clients, and images and other such customizations for each client are done by others.
The directory with these custom images etc. is large, so I left it out of the repo initially. But now those others need to do a lot of work replacing old graphics, so I added the images dir and subdirs so there'd be a safe place for them to get their old versions back and we wouldn't end up with dozens of files renamed to OLDfoo.bar. Now that I've added these image dirs, fossil is inconceivably slow. `fossil status` takes 45 sec on my dev machine, 4.5 minutes on the server. Trivial commits take minutes. The fossil repo is about 1GB. Is this expected-ish behavior for a repo with many files at 1GB? If I delete all these images from any branch I work with, will it get fast again? -- Joshua Paine LetterBlock: Web applications built with joy http://letterblock.com/ 301-576-1920 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
