Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am looking at implementing a simple SVN for our design department. I am leaning towards SVN with Versions (OS X client).

We have about 3 TB and growing of design images.

I'm curious how SVN handles large image files, and a very large amount of them.

share|improve this question
I'm going to try a test with some data that is mirrored from the working directory and see how much it grows. – brennanag Nov 14 '10 at 11:30
up vote 2 down vote accepted

Yes it will require a large amount of space.

It just stores them as blobs of data. There will be no diffs created for them. It will continue to grow every time a file is committed.

share|improve this answer

It will obviously take a good bit of space, considering you have terabytes of data. Storing the revisions will expand rather quickly, considering SVN doesn't have the best binary diff system.

I would look into a version control system that does offer strong binary difference tracking (can't think of any off the top of my head, sorry), and see if that can save you some time and space.

In general, you probably can make SVN work for this, at the cost of a good bit of space. Performance depends on how many files you're working with, also.

share|improve this answer

It depends if content is already in compressed format or not. Subversion uses zlib compression, so repository itself may require less space than working copy if most of it compressable at decent ratio.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.