Menu
This issue is related for operations with TortoiseSVN 1.7 only and on network share only.
On the dev server I have an svn working copy where I can commit something and then update on production server.
Sometimes when all active sessions on the dev server are busy (I can't connect by RDP), I make "Commit" by network share from another dev server.
So, I open DEV-2, then open network directory: \\DEV\Project and click "Commit" or "Check modification".
At this moment dialog opens very slowly (30-40 minutes). There are no unversioned files. And no matter how many changed files (can be 0).
Note: "Update" operation works fine.
Also above issues works fine with old versions of TortoiseSVN (1.6 for example).
I saw many suggestions to not use those operation on network shares, and use them locally.
But this is not a solution of a problem.
Sometimes I need to do "commit" on network share.
And again, this works fine in early versions.
Maybe someone knows how to workaround this problem? Or maybe there exists some setting which can be disabled?
I found same question on tortoise developers forum. But also without solution: http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2892466
428
The main difference between SVN and TortoiseSVN is that the SVN is a distributed version control system while TortoiseSVN is an SVN client implemented as a Microsoft Windows shell extension. In brief, SVN is a version control system. On the other hand, TortoiseSVN is a Subversion client.
TortoiseSVN Version 1.8. 2 has been tested with the ASAM SVN server and is guaranteed to be compatible. However, newer versions should also work as TortoiseSVN is typically backward-compatible to earlier server versions.
The key argument is that SVN due to its support for atomic transactions needs to do many more file operations than CVS in order to ensure integrity. This makes it slower than CVS, especially if there is an on-access virus scanner involved.
That means the Subversion status is normal. As soon as you start editing a file, the status changes to modified and the icon overlay then changes to a red exclamation mark. That way you can easily see which files were changed since you last updated your working copy and need to be committed.
The original poster in a later post in the tigris.org thread that you linked to says:
"I found the solution. If i deactivate
Settings->General->Dialogs 2->Status->"Recurse into unversioned folders"
all works like before with TortoiseSVN v1.6.x."
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2893160
168
Are you using the file:// protocol? If you are, stop it now -- especially on a network share.
You should never, ever use file:// on a Subversion repository -- especially if multiple users are using it.
This is especially true since it is so easy to get svnserver, the lightweight Subversion server process, up and running. There are even directions to get this to work as a Windows Service.
The only issue is that your site blocks port 3690 on your network. However, this should be pretty easy to remedy. If not, you could get one of the many free Apache HTTPD/Subversion packages from VisualSVN, Wandisco, and even CollabeNet that allow you to easily setup a Subversion server using HTTPD on a Windows system.
The only other possible issue is that you're using your old 1.6 Subversion working directory with TortoiseSVN 1.7. The working directory layout for Subversion 1.7 has changed, and you should really do a new clean checkout.
37
As a workaround we have turned of the Show Locks
Right click on a folder and select Tortoise\Settings then General\Dialog 3 then deselect Show Locks
Please have a look at http://tigris-scm.10930.n7.nabble.com/Workaround-for-slow-RepositoryBrowser-on-large-repositories-td92324.html too
41
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
