SVN access became slow

2018-06-05 Thread Johannes van der Vegt
Hi group, Suddenly SVN access became very slow on my PC. Before, everything ran fine. We have a small company network. * "Server" PC: Win10 Pro (1709), runs the svnserve.exe service, version 1.10.0 * My PC: Win10Pro (1803), using SVN 1.10.0-dev (Apr 14, 2018) * Other PC:

Re: SVN access became slow

2018-06-05 Thread Stefan Sperling
On Tue, Jun 05, 2018 at 10:16:15AM +0200, Johannes van der Vegt wrote: > Hi group, > > > > Suddenly SVN access became very slow on my PC. Before, everything ran fine. > > > > We have a small company network. > > * "Server" PC: Win10 Pro (1709), runs the svnserve.exe service, > version

RE: SVN access became slow

2018-06-05 Thread Johannes van der Vegt
Right... I installed a second service with the '-6' option. This did not make any difference. Doing more wireshark sniffing: - At first, SVN client tries connecting from the local-link IPv6 address. There is no response. Two TCP retransmissions fail as well. - Second, SVN client tries connecting f

Re: SVN access became slow

2018-06-05 Thread Stefan Sperling
On Tue, Jun 05, 2018 at 02:54:01PM +0200, Johannes van der Vegt wrote: > Right... I installed a second service with the '-6' option. This did not > make any difference. Why does this not work? This should work. Can you connect to the SVN service with telnet to the server's advertised IPv6 address

Re: SVN access became slow

2018-06-05 Thread Daniel Shahaf
Stefan Sperling wrote on Tue, 05 Jun 2018 15:33 +0200: > If your SVN server has an IPv6 address but does not provide service > on that address, this is expected behaviour. There is no way for > the SVN client to know that it should not be trying this address. Well, connecting to the IPv6 address o

Re: SVN access became slow

2018-06-05 Thread Stefan Sperling
On Tue, Jun 05, 2018 at 01:40:10PM +, Daniel Shahaf wrote: > Stefan Sperling wrote on Tue, 05 Jun 2018 15:33 +0200: > > If your SVN server has an IPv6 address but does not provide service > > on that address, this is expected behaviour. There is no way for > > the SVN client to know that it sho