Hi Brendan, On Wed, May 05, 2010 at 09:21:43AM -0400, Brendan Farr-Gaynor wrote:
> I run a small team of web developers (6) who all work from an in-house > repository. We make lots of commits and often and notice the > performance gets pretty bad. Sometimes taking as long as 2 minutes to > commit a change. We rely a lot on server-side software so we often > need to commit to see what our code will do, this can get painful > during a debug process where as a developer you'll often want to > commit many little changes quickly within the span of 5-10 minutes. I'd rather not commit during debugging, but setup local development environments for the developers so they can work out issues locally, then commit a supposed-to-work version which gets further testinggq. You're really bloating the repository that way (and won't have a useful commit history since most log messages will be empty or "try this" or "..." or whatever). > We're using SVN on a newer quad-core xServe with about 4GB of ram and > a standard 7200 RPM disk (eSATA). Is there something we can do on the > hardware side that would help? Solid State drive? More RAM? Is there > something in our SVN config that I should be playing with? We're > currently using the stock install and config that Apple ships with OS > X Server 10.6 (Snow Leopard). I would not put data on a single disk on any server. It should be at least a RAID-1, especially if you rely so heavily on the repository being available. HTH, Tino. -- "What we nourish flourishes." - "Was wir nähren erblüht." www.lichtkreis-chemnitz.de www.tisc.de