You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Benjamin Adlung <BA...@gmx.de> on 2007/06/01 07:14:17 UTC

Re: svn server hardware requirements

Hi,

marc gonzalez-carnicer schrieb:
 > Our boss has suggested that this machine should be replaced by a more
 > powerful server. Some of us believe this is not at all necessary, and
 > in case it is, there will be time for that.

This in an really interesting article if you plan to add binary-files:
http://www.ibm.com/developerworks/java/library/j-svnbins.html?ca=dgr-lnxw01javapts

Sincerely yours
Benjamin Adlung

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn server hardware requirements

Posted by marc gonzalez-carnicer <ca...@gmail.com>.
hi

2007/6/12, Thomas Harold <tg...@tgharold.com>:
>
> So the new machine is roughly 3x faster for memory intensive and disk
> intensive operations.  If it was Intel architecture, I'd guess the new
> system has a 400MHz (give or take) FSB and that the disks are newer
> 320-500GB SATAs.

correct.

>
> That's generally fast enough to keep a gigabit NIC busy.  You could get
> away with an old 10/100 NIC, but better to use gigabit.  As to how to
> tell... usually the switch lights in the network closet will tell you
> whether it's a 10/100/1000 NIC.  Or you could figure it out in Linux -
> but I'm forgetting how to do that currently.

root@srv-peat-svn:~# mii-tool eth0
eth0: negotiated 100baseTx-FD, link ok


> >> 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.
>
> The box serves multiple needs (the SVN DomU is just one of about half a
> dozen running on that box).  At the time I had limited budget (an
> ongoing issue) and needed to add multiple Linux servers.  It's also
> easier to move DomUs between Xen hosts if the server goes down or as we
> outgrow a box.

Thanks for the input.


> > 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?
>
> http://forums.gentoo.org/viewtopic-t-305871.html
> - Probably the main link
>
> http://www.tgharold.com/techblog/labels/ext3.shtml
> - I also have half a dozen other links on ext3 tuning

Thanks!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn server hardware requirements

Posted by Thomas Harold <tg...@tgharold.com>.
marc gonzalez-carnicer wrote:
> 2007/5/31, Thomas Harold <tg...@tgharold.com>:
>> 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

So the new machine is roughly 3x faster for memory intensive and disk 
intensive operations.  If it was Intel architecture, I'd guess the new 
system has a 400MHz (give or take) FSB and that the disks are newer 
320-500GB SATAs.

That's generally fast enough to keep a gigabit NIC busy.  You could get 
away with an old 10/100 NIC, but better to use gigabit.  As to how to 
tell... usually the switch lights in the network closet will tell you 
whether it's a 10/100/1000 NIC.  Or you could figure it out in Linux - 
but I'm forgetting how to do that currently.

>> 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.

The box serves multiple needs (the SVN DomU is just one of about half a 
dozen running on that box).  At the time I had limited budget (an 
ongoing issue) and needed to add multiple Linux servers.  It's also 
easier to move DomUs between Xen hosts if the server goes down or as we 
outgrow a box.

>> 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?

http://forums.gentoo.org/viewtopic-t-305871.html
- Probably the main link

http://www.tgharold.com/techblog/labels/ext3.shtml
- I also have half a dozen other links on ext3 tuning

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn server hardware requirements

Posted by marc gonzalez-carnicer <ca...@gmail.com>.
Thanks to all who replied, I found your comments very
interesting. I'll comment on some things.


2007/5/31, Nathan Kidd <na...@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 <tg...@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

Re: svn server hardware requirements

Posted by Thomas Harold <tg...@tgharold.com>.

Benjamin Adlung wrote:
> Hi,
> 
> marc gonzalez-carnicer schrieb:
>  > Our boss has suggested that this machine should be replaced by a more
>  > powerful server. Some of us believe this is not at all necessary, and
>  > in case it is, there will be time for that.
> 
> This in an really interesting article if you plan to add binary-files:
> http://www.ibm.com/developerworks/java/library/j-svnbins.html?ca=dgr-lnxw01javapts 
> 

This was also discussed on /. recently (try Threshold=2, Nested, Oldest 
first):

http://developers.slashdot.org/article.pl?sid=07/05/23/1912239

We regularly load 5MB to 50MB binary files (MDBs, images, AVIs) and even 
some 100-500MB MDBs into SVN (svn add / svn up / svn ci) and manipulate 
them with no noticable speed issues.  At least it's never taken more 
then a few minutes to do the check-in, or update.  Our repositories 
range in size from tiny (a few dozen MB) up to a few GB.  Our usual 
bottleneck is either the upload speed of the remote location or the T1 
line going into the main office.

Our primary repository is ~1850 revs, 6.4GB on the server and creates a 
18.7GB working copy with 182,000 files (including .svn/_svn folder 
contents).  I haven't exported it in a while, so I'm not sure exactly 
how many source files there are in the repository.  Most revisions files 
in the FS db/revs folder are in the 1-20MB range, with the top 5 
revision sizes being: 280M, 220M, 125M, 120M and 110M and tailing off 
towards 10M and below (the top 100 revisions are all 14M or larger).

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org