This issue looks to be a bit deeper and out of our control than first expected.
The problem we are seeing where commands such as saving a local copy are taking a long time are occurring due to a clash between the IP versions of the local SVN application and the SVN server.
If you check out a project using an IPv6 name (eg “
svn:/MySVNServer”) but the SVN server is not set up to use IPv6 then it causes multliple commands to be fired off from the local machine’s SVN software to try the same command again using an IPv4 compatible command. To resolve this, you can either make changes on the SVN server, or make changes on how the projects are checked out on your local machine.
If the SVN server is started as a service, enabling the IPv6 option would look like:
C:\Program Files\TortoiseSVN\bin\svnserve.exe --prefer-ipv6 --service -r E:\SVN\Repository
You can relocate an existing local copy of SVN project if the SVN prefers IPv4:
C:\Program Files\TortoiseSVN\bin\svn.exe relocate svn://mysvnserver svn://192.168.1.123 E:/MyProject
Since it seems you are using a third party cloud storage solution (Beanstalk App) to store the SVN projects, I would recommend getting in touch with their support or checking the settings in your profile to see if it’s possible to change over to IPv6.