Talden wrote:
> I mentioned this in another post and was hoping for some comparative
> feedback...
>
> I'm in the process of getting our development teams to move to
> Subversion. Currently our team uses CVS and I've exptrapolated usage
> and content data to guestimate what our subversion usage will be like
> in production. I have no idea what a reasonable hardware
> infrstructure for Subversion is or whether other subversion projects
> have comparable metrics.
You could probably get away with a simple 4-disk RAID-10 SAS/SATA array
using 10k RPM disks. And even that might be overkill.
We have half a dozen users, 15GB of repository data (spread across about
2 dozen repos) and are running a 4-disk 7200RPM SATA RAID10 system on a
dual-core CPU. (Although the SVN server runs in a Xen DomU and is only
allowed access to one of the cores.) I only gave that SVN DomU 512MB of
RAM and it seems to do just fine.
But all of our developers are outside the office, so the T1 line is
really our real bottleneck. We also only have about 1000 revs in the
repository since we did a snapshot of our old VSS system and have only
been using SVN for a few months. I may even move the system over to a
2-disk RAID1 SATA when the next Xen box comes online in a month.
If you use FSFS as the underlying storage, disk seek times and good file
systems probably matter the most. (We're using ext3 with directory
indexing turned on. Which I expect will be fine until we hit the 100k
revision count range. But that's a complete guess.)
It also depends on what access method you use (Apache, svnserve,
svn+ssh). Back when I was doing the import, I think (very vague
recollection) I was seeing data rates in the 3-6MB/s range with 75% CPU
inside the DomU. Which is plenty fast enough to keep up with T1 demands.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 30 06:08:52 2006