Hi, Andreas, Andreas Krey [mailto:a.k...@gmx.de] > But I may be barking up the wrong tree. I built svn 1.7 and ran my small > 'second consecutive commit fails' test script with that. It's not the > local operations, but those that act on the repository (here: > file:///...) that take ridiculously long. Each commit and do-nothing 'svn > up' takes about a second, for the five files involved. I've come to expect > such operations to be instantaneous.
We had similar timing issues when accessing repositories via SharpSVN - but it happened on svn:// and http:// issues - each remote operation expected to take X ms did take (1s + X ms). In our case it was an IPv6 Problem: The server was only reachable on IPv4, but the host name of that server (localhost) did resolve to both an IPv6 and IPv4 address. The Windows 7 IP stack now seems to try an IPv6 connect, and if that fails, waits 1 second until retrying via IPv4. I don't think that both problems are related (especially as that happened to us using Svn 1.6), but the effect seems to be the same. :-) Best regards Markus Schaber ___________________________ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber | Developer Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50 Email: m.scha...@3s-software.com | Web: http://www.3s-software.com CoDeSys internet forum: http://forum.3s-software.com Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
