How to change from https:// to svn:// protocol in subversion server

UPDATE : svn and http protocol benchmarking is in..

How long it took to checkout the trunk of a project (in minutes and seconds)..

svn protocol : 5:32

http: protocol : 5:33

svn protocol (with AVG folder exception) : 2:22

http protocol (with AVG folder exception) : 2:23

Speed Result : Absolutely nothing in it!

AVG Result : However by telling AVG to ignore my working copy folders checkout time became tw开发者_开发问答ice as fast!

ORIGINAL QUESTION :

We currently use VisualSVN Server that I think!? only supports http(s) protocol? (Can someone confirm?)..

I have read here and realise that the svn:// protocol is considerably faster especially with lots of smaller files.

Can anyone recommend the most pain free way of migrating to using a subversion server with the svn:// protocol (even if that means using a different flavour of subversion server).

The machine running VisualSVN Server is a Microsoft Windows Server 2003 box.

Thanks in advance,

-- Lee

recommend the most pain free way of migrating to using a subversion server with the svn:// protocol

Use original Subversion server instead of VisualSVN. Administrating repository is not so hard! Just move to normal SVN and save yourself license costs.

Also I would suggest to stay withing HTTP/HTTPS protocol. In most of cases, protocol is not an issue on Windows work stations. The issue usually your Antivirus and slow NTFS that cause the problems.

General note: checkout on Linux is faster by order of magnitude then on windows station because of the above issue. So I don't believe it would feel any improvements after switching to svn://. Also you may do some simple benchmarking with original Subversion server and check if it improves anything.

Also, working with https allows you (at some point if you want) to put SVN repository in internet and allow users to access it in secure way without VPN.

I think it is easy to change from https:///http:// to svn:// protocol in VisualSVN server since there is a svnserve under VisualSVN server. Just to start the svnserve use the command svnserve -d -r <repositories_dir>, then you can use svn:// protocol to access the repositories.

It turns out the problem with subversion update slowdown was NOT due to the protocol (SVN was the same speed as HTTP) but in fact due to AVG scanning every file.

After adding an exception to AVG to ignore my working copy folders updates and checkouts are now more than twice as fast.

How long it took to checkout the trunk of a project (in minutes and seconds)..

svn protocol : 5:32

http: protocol : 5:33

svn protocol (with AVG folder exception) : 2:22

http protocol (with AVG folder exception) : 2:23

Speed Result : Absolutely nothing in it!

AVG Result : However by telling AVG to ignore my working copy folders checkout time became twice as fast!