On Fri, Sep 17, 2010 at 03:15, Keith Moore <keith.mo...@securency.com> wrote: >>-----Original Message----- >> From: Gary [mailto:subversion-u...@garydjones.name] >> Sent: Friday, 17 September 2010 16:24 >> To: users@subversion.apache.org >> Subject: Re: Choosing a server >> >> Johnathan wrote: >> > There's not much that Subversion cannot run on. >> >> No, sure :) I was really looking for hints as to what general properties >> a server should have. For example I would suspect that CPU speed isn't >> much of an issue because actually the server is only "active" >> occasionally, whereas storage reliability would be a major >> requirement. Like I said, I have my own ideas but was interested in >> others' input as well. >> >> If it should be Linux, BSD, whatever, is less of an issue because we >> already have sooooo many variations in use *rolls eyes* >> ---------------------------------------------------------- > Well for what it's worth we run svnserve.exe on Windows Server 2003 R2, > virtual server on VMware ESX. > The virtual machine has 1 CPU, 4GB of RAM, 1 Gbit network adapter. The hard > disk is on a SAN and connection is via iSCSI. This is running really well > for us.
That's pretty much my setup as well, but I think I'm only using 1GB or 2GB of RAM. Recently I've noticed some slowdowns on checkins of binaries but I think my disk is on some of our slower SAN space, which would make a big difference. The only drawback to running a Subversion server on Windows is that most hook scripts assume that you have the typical *NIX environment - can run just about any scripting language, sed/awk/grep are all available, etc. Not that you *can't* manage this on Windows as well, it's just a little extra work.
