Re: Howto prevent svn from storing deltas for binary files

Hi,

> I would like to take incoming deliveries of a subcompany under version
> control. Most of the files are binary (c/c++ libraries).

> When doing a usuability test with svn I found that a library of about 9 MB
> increased the repository size by about 24-28 MB.

> My conclusion is that a library as a result of a compilation might change
> completely leading to a storage effort for tracing the changes that is
> higher than original file itself.

Did you verify which files caused this increase in size? I think it
may be caused by unused logs laying around in your repository db/
directory.

Also, if you import it the first time, maybe the increase is 24MB, but
how much increase do you see the second time you commit a library to
the repository? I don't think bdb gives back any unused space in its
db files to the filesystem, but reuses it on next occasions.

> Second the reponse time for switching
> between the versions takes to much time (about 30 seconds for a total of 13
> MB and a local repository accessed by file://)

This is possibly due to the fact that the ra layer is generic and
unaware that there is no network communication. So it calculates a
diff against the version you have in your tree. After 'sending' it,
the diff is applied. Which costs a lot of CPU. Unfortunately, there
currently is no way to tell Subversion you are working locally.

> Is it possible to prevent svn from tracing the changes and simply store a
> clean copy instead of a diff ?

No. I'm sorry, but I don't think seeing an increase of 24MB on
committing a file of 9 MB is caused by Subversion's diffing routines.

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 7 16:13:45 2004