We use subversion in a corporate network with different locations. It
is absolutly nessesary to use a network share. A local working copy is
no option in our environment.
I think the problem is not the database or the network share.
TortoiseSVN seems to read/analyse every file in the working copy on
the network share. But the question is why? In my opinion only the
~1000 versioned files needs to be checked and not the whole 250.000
files, because most of them do not stay under version control.
Cleanup or anything else do not help...
On 12 Dez., 13:02, Andy Levy <andy.l..._at_gmail.com> wrote:
> On Mon, Dec 12, 2011 at 05:15, Lübbe Onken
>
> <luebbe.tortoise..._at_googlemail.com> wrote:
> >> Canonical answer: Move your working copy from the network share to a
> >> local drive. That's highly recommended anyway.
>
> > A cleanup of the working copy might help too. It is possible that due to
> > timestamp differences, Subversion scans all the files in the folder for
> > changes.
>
> > But anyway: Move yor WC to a local disk. That's recommended best practice.
>
> There was some discussion on the SVN Users list a few weeks ago around
> the performance of SQLite on a network share (NFS mount in that case).
> That was dealing with how svn rm scales but may apply here as well.
>
> Start athttp://svn.haxx.se/users/archive-2011-10/0891.shtml
>
> ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess...
>
> To unsubscribe from this discussion, e-mail: [users-unsubscr..._at_tortoisesvn.tigris.org].
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2892537
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-12-12 16:47:08 CET