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

Re: how issue-2897 branch solves reflective merges?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 21 Jan 2008 14:07:41 -0500

Mark Phippard wrote:
>> Node-origins in FSFS can be done by writing a single file for each node-id
>> which contains the origin value into a 'node-origins' subdirectory. We'd
>> probably want to shard that in some fashion -- we have around 5000 origins
>> to store for the Subversion source code repository today.
> If we have to create an object in the file system for every node in
> the repository is this potentially a problem waiting to happen? Are
> we going to be greatly increasing the size of the repository and the
> demands on the server file system? An svn import of thousands of
> files would have to create thousands of these items too right?

Greatly increasing repository size? Not likely. We're talking about a
mapping of node-ids (a single base36 number) to node-revision-ids (one of
those dotted triplet thingies).

And yes, an import of 2000 files/dirs would create 2000 of these records.
But if in the next commit you changed all 2000 of those things and
committed, no new records would be created -- they only show up for brand
new lines of history.

> Do we have an official goal to remove SQLite as a dependency now?

I'd certainly like to see it happen, but that's just my personal preference.

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2008-01-21 20:07:54 CET

This is an archived mail posted to the Subversion Dev mailing list.