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

Re: Size comparison repository - working copy

From: Talden <talden_at_gmail.com>
Date: Wed, 9 Jan 2008 15:25:03 +1300

On Jan 8, 2008 9:57 PM, gec9_at_swissonline.ch <gec9_at_hispeed.ch> wrote:
> The directory containing my SVN repository has 1.5 GB but after checkout the
> directory with the working copy has 18 GB! How can it be?! I was thinking that
> the repository and the working copy have roughly the same size.
>
> Thanks
> Gec

This makes perfect sense. Consider the following tree of folders/files

dev/
  SecretQuoteLaserUnquoteProject/
    branches/
      thatReleaseWeDidBackInNam/...
      thatReleaseWeDidJustTheOtherDay/...
    tags/
      inchstone1/...
      milestone1/...
      austone1/...
    trunk/
      SecretBlueprints.Hires10000000ByteVersion.txt

If those tags are all copies of the trunk at various points in time
and only a few KB of changes are made each revision to the file in
trunk then in the repo those tags take very very little space. So in
the repo we have:

The space for the initial tree and diffs for each revision + very
cheap copies for each tag (I'm ignoring properties, skip-deltas ,
content compression and any structural and revision metadata here).

If you check out this entire tree you'll get six copies of the trunk
at various points in time including 6 different versions of that big
file. In general usage you should check out only the trunk, a single
branch or a single tag and in those cases you'd get only a single copy
of the big file.

Are you checking out a whole tree containing tags and branches when
you really are only interested in a select part of the tree?

--
Talden
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-09 03:27:09 CET

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.