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

Re: Server Specifications and Architecture Question

From: David Ripton <dripton_at_ripton.net>
Date: 2005-01-21 20:43:02 CET

On 2005.01.21 10:45:44 +0000, Kris Syverstad wrote:
> We are in the process of moving over to SVN and are trying to figure out
> what type of infrastructure we should implement. Typically we have
> around 6 projects ongoing with about 50 developers. There doesn't seem
> to be a lot of sizing information available for SVN, which brings me to
> my questions.
> Can SVN use our SAN for storage? (We are two weeks out from our SAN
> being up, otherwise I would just try it...)

BDB is not supported on networked filesystems. If you're lucky it will
just fail right away; if you're not it will wait until just the wrong

FSFS will work on some networked filesystems, like NFSv3. Read
http://web.mit.edu/ghudson/info/fsfs for details.

Even with FSFS, I'd to put the repository on a local drive rather than a
networked filesystem if at all possible. Why add the network overhead
and the extra potential locking bugs if only the SVN server needs to see
the files?

> If we use a box with the following specs and attach it to our SAN, does
> anyone see any potential problems given number of projects/users?
> 1 x 2.4-GHZ Pent
> 1GB mem
> Embedded ATA-100 IDE controller
> Embedded 10/100/1000GB NIC

That hardware looks fine. (Though you meant Mbps not GB on the NIC.)

David Ripton    dripton@ripton.net
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 21 20:45:17 2005

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.