Reducing the size of the .svn folder

76
votes

In our project we made the decision to reduce the build time by using pre-built binaries. Weekly/monthly we create a stable release and commit it to the repository. The build uses these binaries instead of building everything from source.

For build speed this is fantastic. But, unsurprisingly, it really bulks up the SVN checkout size. Our trunk currently sits at ~22 GB. I realize this is not the intended usage of Subversion. But we don't have an alternative at the moment.

But I'd like to improve the current situation. The .svn folder makes a big contribution to the size of trunk on disk. When the binaries are updated, it seems to keep several bases in the .svn folder. That is, if a binary is 4 GB there is a copy in the .svn. If it's updated then the .svn folder holds the original base plus the new base and bulks up to 8 GB for that one file.

Is it possible to tell Subversion not to keep a base in the .svn folder for certain files? Through google I found a similar question, How to decrease .svn folder size?.

The answer Simon received was

  • Use a partial checkout (which won't work for me as I need the binaries)
  • This is not yet a feature of Subversion
  • It was discussed, but will not be a feature until at least Subversion 1.8

Luckily for me subversion 1.8 has been released. Was this feature added?

I did not notice it in the release notes. Though "Directory and property storage reduction" looks promising.

2
svnsizesvn-checkout
This is not really where subversion shines - you should look into artifactory or nexus to store the artifacts and resolve (fetch) them with your build script. – thekbb
Sadly we knew this. But its just so convenient to use svn. In the past, on another project, we employed Maven. But, apparently, that left a bad taste in a lot of peoples mouth. Next came a custom tool that I can only describe as Maven like (but which, of course, solved all Maven's problems). That too left a bad taste. In our latest project we just ended up leveraging svn. – Shane Gannon

2 Answers

76
votes

There's no way to get rid of the need to store pristines at this point. It's been talked about but it's actually not an easy problem to solve because there's so many different use case situations that would be presented by removing them optionally.

With 1.7 the pristine storage was changed and in some cases you may actually see the situation as worse than before 1.7. Pristines are now stored in files named by the hash of the pristine. So if you have multiple identical files you won't have duplicate pristines stored. However, we also don't cleanup pristines anymore. So they just continue to build up. You can trigger unused pristines to be removed with svn cleanup.

There is a point to keeping unused pristines around, if you're switching between branches we no longer have to download things that you already have the pristine for in 1.8.

43
votes

For those using TortoiseSVN client's Cleanup command rather than svn cleanup command, .svn folders size can be decreased by making sure that Vacuum pristine copies option is checked:

enter image description here

Also, it is recommended to cleanup at the top level of the working copy, as indicated here.

[Edit]

According to this answer and SVN change log, svn cleanup has an option to vacuum pristine copies (/vacuum). This is done by default starting from 1.8. From version 1.10 up it is not longer done by default, but can be run using the command svn cleanup --vacuum-pristines (see this answer).