Right, again, need a Linux machine for this. :-)
Maybe I need to look for a professional SVN hosting with state of art
environment to make sure everything runs fine. 500,000 revs should be enough
for my any near future concerns (5 - 10 years later? We will have new system
anyway).
Another concern is performance. I keep seeing the word "time out" when I
read the book. The word "wedge" keeps me away from bdb, but the "time out"
is also scary.
When you check out a repository or commit a change, is SVN smart enough to
keep this operation a constant time frame, disregarding how many revs you
have? I feel like SVN has to re-calculate everything from rev0 in order to
reach the final state of every file in the repository.
Anyway, I like the FSFS approach, but the scalability is a real concern. I
am wondering why it's not a concern when the approach is decided, as it's
easily to partition the files in to a decent hierarchy folder structure
without too much work.
Calvin
-----Original Message-----
From: Marc Sherman [mailto:msherman@projectile.ca]
Sent: Sunday, July 17, 2005 12:07 PM
To: users@subversion.tigris.org
Cc: John Szakmeister; Calvin
Subject: Re: SVN Security
Ben Collins-Sussman wrote:
>
> KDE has ~500,000 revisions in their one repository, and I think it's
> using FSFS. No problems reported.
They're probably not hosting their repository on NTFS, though.
- Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 17 18:30:27 2005