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

Re: Repo packing with subversion 1.6 results

From: B Smith-Mannschott <bsmith.occs_at_gmail.com>
Date: Fri, 27 Mar 2009 06:54:46 +0100

On Fri, Mar 27, 2009 at 02:45, svnuser <jzaniewski_at_gmail.com> wrote:
> I have sharded repo using 1.5.6 with 22K revisions, size 2.9G
> I loaded its dumps into a new repo using 1.5.1 (I meant to use 1.5.6 but
> this should do)
> My new repo has the same size as my original (expected).
> I run upgrade/packing on it with 1.6 and all I save is 100M.
>
> I load the dumps again but this time I use 1.6 and my repo is now 2G. I do
> the packing and my repo shrinks by 100M.
>
> Are these expected results?

Yes

> Why such diff in size loading with 1.6?
> btw my repo is mostly source code but I do have some binaries.

<http://subversion.tigris.org/svn_1.6_releasenotes.html#filesystem-improvements>

# Sharing multiple common representations (issue 2286, server)
# ------------------------------------------------------------
#
# When using many branches and merging between them often, it is common
# to have files with similar lines of history which contain the exact
# same content. In the past, Subversion has stored these files as deltas
# against previous versions of the file. Subversion 1.6 will now use
# existing representations in the filesystem for duplicate
# storage. Depending on the size of the repository, and the degree of
# branching and merging, this can cause an up to 20% space reduction for
# Berkeley DB repositories and a 15% reduction for FSFS repositories.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1440247

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-27 06:55:42 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.