I’m planning on setting up an svn repository which will contain 3rd party binaries that various product builds at my work place will depend on. since these are all binaries and not text files any addition to this repository will duplicate the artifacts and i’m a bit concerned about size limit.
right now i’m looking at ~15 GB of binaries, and i know 350GB is possible (as evident from this question – 350GB SVN repo creates atleast 1MB revision for even a simplest task like branch/tag).
i also know there are limitations imposed by the underlying operating system (2GB max singel file size for example, which i dont expect to hit), and there’s no hard limit in the svn code.
what im asking is how large have people seen svn get without major issues? also keep in mind this repository will be (relatively) seldomly updated – about once every few weeks.
my options for operating systems are windows x64 (server 2008, most probably) and linux x64 (probably red hat ent.). file systems will be ntfs in windows and whatever i want on linux.
clients will mostly be tortoise svn 1.7
so what are the practical limits in my case?
First of all, Subversion is a modern version control system, so binary data as such isn’t an issue. Subversion can create deltas from binary data, so the commits will be as small as possible.
The problem is usually that binary data actively prevents to generate small deltas. One reason is that binary data can be compressed and that usually causes huge differences.
That said, your repo probably won’t grow extremely fast anyway. We have a big product which currently uses about 400 third party dependencies. Every month, a couple of those change. Or to put it another way: Your dependencies won’t all change every week. That means you will only add a few MB per month (unless you have a really unstable dependency which changes a lot but again, most dependencies aren’t like that).
So my gut feeling is just to try it and solve any problems as they show up because there probably won’t be any big/unusable problems anyway.