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

Repository sizing and infrastructure requirements.

From: Talden <talden_at_gmail.com>
Date: 2006-11-29 01:39:40 CET

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.

I'm showing you mine, will you show me yours...

I expect we will maintain 2 repositories, one highly active, the other
merely present for rare maintenance tasks.

  Legacy/unmigrated projects
  20,000 files, 3,500 folders, <500 commits per year.
  Working copy 2.5GB. (excluding .svn)
  Typical commits ~10 files, ~100kb diffs in total.

  18,000 files, 5,500 folders, 8,000-10,000 commits per year.
  Working copy contents 1GB. (excluding .svn)
  Typical commits ~10 files, ~100kb diffs in total.

3 teams of 10 devs each will hit the Main repository 99% of the time.
Working hours for each team only overlap by a short period as we are
spread around the globe about 6-8 hours apart. One team is local (LAN)
to the server

NB: High-latency, low bandwidth connections suck big-time with CVS for
the rest of

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 29 01:40:14 2006

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