AW: Re: Large repository - slow svn update
From: Felix Gilcher <gilcher_at_exozet.com>
Date: 2005-12-08 18:02:30 CET
Andy Levy <mailto:andy.levy@gmail.com> schrieb am Donnerstag, 8. Dezember 2005 17:20:
> On 12/8/05, Daniel Montero <danim@soin.co.cr> wrote:
Even if it were lock-based you'd have to update you version before changing it - locks only prevent concurrent updates. But you always have the option to just update what you need (individual files, directories or partial source trees) however you might run into problems if one change depends on another somewhere else.
However, you can enforce locking in svn if you prefer - see the svn:needs-lock property.
>
You could use a differenct access method. Some users have reported significant speed improvements after disabling on-access virus scanners (subversion walks the directory tree to determine which version of which files you currently have, this process is slowed down by on-access scanners).
>> So what can I do in order to accelerate the svn update for my
Even if it were that simple, you'd be more or less on your own if you introduce a bug - so I'd be careful. Your VCS is supposed to safeguard your most valuable asset, your source code and I'd not feel comfortable using a "hacked" version in production. At least test your changes properly.
>
just my $0.02
felix
-- Felix Gilcher Head of IT Development Exozet Berlin GmbH Rotherstraße 20 10245 Berlin --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.orgReceived on Thu Dec 8 18:21:03 2005 |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.