On Wed, Feb 8, 2012 at 11:05, Richard Hipp <[email protected]> wrote: > Probably what happened is that you did some operation that created a large > "undo" stack, which was stored in the _FOSSIL_ file. Then later, after the > undo expired, that space was freed. If the space utilization is an issue > for you, you can do this: > > sqlite3 _FOSSIL_ 'PRAGMA auto_vacuum=FULL; VACUUM;' > > And then the space will be automatically reclaimed in the future. > > I generally don't stress over a 10MB file on my 1TB disk drive, though... >
Richard, thanks for the tip. After vacuuming _FOSSIL_ size reduced from 9.7MB to 160KB. Speaking of disk usage. Here at AT&T Labs I am running multiple virtual machines each having a shoe-string budget of 10 to 20GB disk space per machine. On that scale 10MB times number of open fossil repos is noticeable. --Leo-- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
