gmu 2k6 wrote:
> On 7/8/06, Nico Kadel-Garcia <nkadel@comcast.net> wrote:
> well, I might still try XFS as it is told to cope better with hardware
> failure, though the diskarray should take care of that in the first
> place :). it might not hurt to compare ext3 and XFS.
Don't forget to set up hdparm to tune any IDE disks: the performance benefit
from setting such drives to UDMA/ATA behavior with "hdparm -d1c1 /dev/hda"
rather than the very conservative default settings is huge and easily
overwhelms benefits from clever filesystems.
>>> the second big question I have is whether there is a performance
>>> problem with stuffing all of the dirs as outlined above into one
>>> repo or using separate repos. when using svnserve without ssh and
>>> many repos this would of course mean that I have to maintain
>>> multiple access-control configs and sync the password files.
>>> therefore for creating multiple repos to be used by the same groups
>>> of devs it may be best to use svn+ssh and rely on xattr or go with
>>> WebDAV although I really want to avoid Apache for security and
>>> performance reasons.
>>
>> Hah. I've dealt with this. Welcome to the world of Apache password
>> files, which can be entirely shared for a master directory, and the
>> additional layer of user access avaiable through svnperms.py and
>> svnperms.conf, which can be symlinked into every repositoriies
>> configuration.
>
> now that I've re-read the 1.3 release-notes: can't I just do this with
> a shared authz-db file?
Yes, but I really, really hate the authz-db file's reliance on non-encrypted
passwords. Apache provides robust password encryption end-to-end with HTTPS
and htpasswd. And it's easy to set up something like Webmin to manage the
accounts and passwords for htpasswd, or to set up Apache to use an LDAP
backend for user passwords. svn+ssh helps avoid this, but the web access to
the repository and ease of setting up a "wget -r project/trunk" helps ease
downloading and web access to the whole repository as desired.
>>> the third question mark in my head is: what setup do people like
>>> apache.org, kde.org and other big projects with many binary files
>>> and text files use?
>>
>> Sourceforge: lots of projects, many of which are huge but most of
>> which are functionally distinct from each other and have their own
>> codebases.
>
> yeah, but they all use separate repos, as does most probably Apache
> too.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 8 16:04:02 2006