[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Logfile growth

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2004-07-30 15:42:35 CEST

I am evaluating SVN with the Tortoise front end for use in our organisation.
So far it all works very nicely, except for the fact that the DB logfile
seems to keep growing and is *much* larger than the data. To put this in
perspective, I am only using 12 source files (text), totalling 72K. The
strings file is 120K which is reasonable, but the log file is now 1MB. This
is of course tiny compared to a real project, but if it scales up in the
same proportions then it will make for a huge log file.

Steps so far:
Create local repository using TSVN
Add 12 files
Modify the first few lines a couple of files several times with commits,
  including adding keywords.
Now at revision 16.

Now every time I do something simple like an update of my WC directory, I
add 4K to the repo logfile, even when the update changes nothing. I have
tried 'svnadmin list-unused-logs c:\temp\testrepository' and got blank
output, from which I assume that the logfile is not unused, and therefore
cannot be deleted. I have also tried deltify, and that grows the logfile
again. I assume that the deltify is actually happening automatically on
commit, but thought I had better try it anyway.

I cannot find anything about this in the FAQ, either for SVN or Tortoise.
Should I expect the logfile to grow without bounds or have I missed a vital
admin process somewhere? Once the actions have been carried out on the
database, why is the logfile still needed?

Simon.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 30 16:13:23 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.