TortoiseSVN shows the log very slowly on a working copy stored on a network share

I am using a working copy stored on the samba share. It seems to be working fine; ecxept ...

Under the windows, I can do "svn log -l 100 -v". on a working copy and get results in <1 second. However, if I use TortiseSVN to right-click and display the log, it freezes for several minutes when using> 30 Mbps network bandwidth.

Are there any known problems or configurations that Tortise needs to process a saved working copy of the network?

+4
source share
3 answers

I understand that this thread is a little old, but ... I found it, so someone else is likely to find it. This is not necessarily the solution that I know, and what I have experienced in the past and most recently.

I studied this question for a long time. We are suffering from the same problem. Sluggish response time on Windows workstations + Linux web servers with SMB shares that host each user check.

The time taken to commit / update / request is terrible. We all just learned to live with him because of how our development environments are defined. They are all semi-remote, not on our local machines, which is sad for developers, but how did the security officer and system administrator do things back when.

To be fair and not blame it all on TortoiseSVN, we had problems with sluggish response times in other applications. I personally experience terrible delays when editing any code in my checks using Eclipse.

TortoiseSVN seems to have added some information to its FAQs since I last looked (forever):

Can I create a local repository in a network directory? http://tortoisesvn.tigris.org/faq.html#repoonshare

Can I save my repository on a network resource instead of setting up a server? http://tortoisesvn.tigris.org/faq.html#reponoserver

+1
source

I think the following link describes how svn 1.7 made this "working copy of subversion on a network drive (nfs / samba)" even worse than in svn 1.6:

http://svn.haxx.se/dev/archive-2012-02/0413.shtml

It would be great if svn 1.7 had the option to enable this exclusive SQLite locking mode.

+1
source

You should not put working copies on network drives!

-1
source

Source: https://habr.com/ru/post/1340036/


All Articles