Menu
I'm using a working copy stored on a samba network share. It seems to work fine; except...
Under windows I can do "svn log -l 100 -v ." on the working copy and get results in <1 second. However if I use TortiseSVN to right click and show log it hangs for several minutes while using >30Mbps of network bandwidth.
Are there known issues or configs needed for Tortise to handle a network stored working copy?
998
TortoiseSVN cache process checks repository checkouts for changes and displays nice overlay icons in Windows Explorer. Instead of disabling the cache, you can optimize the paths where TSVNCache.exe looks for repositories so it only actually looks at working copies and not your whole disk(s) drive(s).
However, newer versions should also work as TortoiseSVN is typically backward-compatible to earlier server versions.
All files and folders that are not versioned are moved to the trash bin. Note: you can also do the same from the TortoiseSVN → Revert dialog. There you also get a list of all the unversioned files and folders to select for removal. This command reverts all your local modifications which are not committed yet.
Security-wise, it doesn't run anything that should be remotely exploitable and if you've got local exploit issues on the server then you probably need to rethink your security policy. The biggest issue if these are web apps is that the . svn folders on windows could potentially be read depending on server setup.
I realize this thread is a little old, but... I found it, so someone else will likely find it too. This is not necessarily a solution it's what I know, and what I've experienced in the past and more recently.
I looked into this issue quite a while ago. We suffer from the same issue. Sluggish response times on Windows workstations + Linux web servers with SMB shares that house each user's checkout.
The amount of time it takes to commit/update/query is dreadful. We've all just learned to live with it because of how our development environments are defined--They are all semi-remote rather than on our local machines, which is sad for developers, but it's how the security officer & sysadmin decided to do things way back when.
To be fair, and not blame it all on TortoiseSVN, we've had issues with sluggish response times in other applications too. I personally experience horrible delays when editing any code in my checkouts using Eclipse.
TortoiseSVN has apparently added some info to their FAQ since I last looked (forever ago):
Can I create a local repository on a network directory? http://tortoisesvn.tigris.org/faq.html#repoonshare
Can I keep my repository on a network share instead of setting up a server? http://tortoisesvn.tigris.org/faq.html#reponoserver
122
I think the following link describes how svn 1.7 in general made this "subversion working copy on network drive (nfs/samba)" even worse than it was in svn 1.6:
http://svn.haxx.se/dev/archive-2012-02/0413.shtml
It would be great if there was a option in svn 1.7 to turn on this SQLite exclusive locking mode.
45
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
