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

Re: svn server hardware requirements

From: marc gonzalez-carnicer <carnicer.lists_at_gmail.com>
Date: 2007-06-05 11:40:47 CEST

Thanks to all who replied, I found your comments very
interesting. I'll comment on some things.

2007/5/31, Nathan Kidd <nathan-svn@spicycrypto.ca>:
> > * what hardware configuration are you using on your servers? have you
> > brought back to life forgotten machines? or are you using brand new
> > servers with xeons / dual core and raid?
>
> Think of it this way: When you drive a Corolla it works fine and you
> get where you want to go without complaint. However, after you drive a
> BMW 5-series sedan you won't want to go back to the Corolla.

:)

I was thinking of the same kind of reply, using cars as
a comparison. It is also a matter of budget. Think of a
guy who runs a small building business. He may have
enough money to buy a luxury car, but he won't carry
his everyday tools on it. Insted, he shall buy a van for
working and a less expensive car for personal / family use.

2007/5/31, Thomas Harold <tgh@tgharold.com>:
>
>
> Everyone's access patterns are different, which is why I suspect there
> isn't a page for it.

Hmm, I somehow disagree. If svn is supposed to be
quite resource efficient, as opposed to the more
bloated alternatives, why not provide some system
configuration range patterns depending on the
number of developers?

> > * is the above mentioned hardware configuration enough to serve 5 - 20
> > developers?
>
> At a minimum, I'd make sure that you're running RAID1 with a hot-spare

using raid1 is a good suggestion.

> disk. But the other issue you'll have with an older system is bus
> bandwidth (PCI and chipset). When you run hdparm -tT /dev/sdX, you'll

these are my figures. btw, how can i know the NIC specs? :

* srv-peat-svn : (old machine)

     root@srv-peat-svn:~# hdparm -tT /dev/hda4
     /dev/hda4: (ext3)
      Timing cached reads: 424 MB in 2.00 seconds = 212.03 MB/sec
      Timing buffered disk reads: 68 MB in 3.02 seconds = 22.55 MB/sec

     root@srv-peat-svn:~# hdparm -tT /dev/hda2
     /dev/hda2: (ext2)
      Timing cached reads: 492 MB in 2.01 seconds = 245.35 MB/sec
      Timing buffered disk reads: 66 MB in 3.00 seconds = 21.99 MB/sec

   * bub : (new machine)

     bub:~# hdparm -tT /dev/sda5
     /dev/sda5: (ext3)
      Timing cached reads: 1710 MB in 2.00 seconds = 855.07 MB/sec
      Timing buffered disk reads: 114 MB in 3.04 seconds = 37.47 MB/sec

     bub:~# hdparm -tT /dev/sda7
     /dev/sda7: (ext2)
      Timing cached reads: 1740 MB in 2.00 seconds = 869.64 MB/sec
      Timing buffered disk reads: 194 MB in 3.01 seconds = 64.54 MB/sec

> Our current SVN server is a Xen DomU running on top of a dual-core AM2
> ...

impressive. however, i can't figure out why would anyone use
virtualization to run a server. i am not saying it is not correct, it's
just i'd never consider it.

> revision files (assuming you use FS and not BDB). If you use ext3, that
> means you really need to turn on directory indexing (because all
> revision files end up in a single directory). So a 4-disk RAID10 would

yes, i do i plan to use ext3 so that data may be safer in case of
power / system failure. how to turn on indexing?

> Going the white-box route, figure $700 for a good server case (like the
> ...

thanks for the figures

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 5 11:41:29 2007

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