[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Problem with many svn operations in a short time

From: Bert Huijben <bert_at_qqmail.nl>
Date: Wed, 13 Aug 2008 15:10:38 +0200

> -----Original Message-----
> From: Michael Pfob [mailto:m.pfob_at_3s-software.com]
> Sent: woensdag 13 augustus 2008 13:43
> To: dev_at_subversion.tigris.org
> Subject: Problem with many svn operations in a short time
> Hello Subversion Developers,
> In my application, that is based on subversion, it is possible that
> many
> svn-operations are issued in a short period of time. In a windows
> environment, problems will appear when you try to execute ~4000 svn
> commands (like svn_client_log, svn_client_cat) using the svn protocol.
> The reason for this problem is that windows does not allow to reuse the
> client side of the sockets until about 4 minutes have passed. This
> means
> that it is not possible to execute more than 4000 subversion operations
> in less than 4 minutes in a windows system.

        Hi Michael,

Are you sure the limit is in Windows and not in some kind of firewall

I know that ISA server imposes some of these limits and probably many other
firewalls and maybe even routers do. (I had to lift those rules before we
introduced a batch processing webrequest in one of our products at work).

I can't imagine a case where executing 4000 svn_client_* function calls
would really make sense.
Most commands I would repeat allow multiple targets in 1.5. (But I know some
of those are implemented as a top level loop over the parameter, so this
wouldn't really help in this case.. But without those variants there is not
much that can change as the client api doesn't keep connections open over
different function calls).

(Maybe you should look at the lower level c-APIs to take advantage of a
reusable session for your specific use case)

> I think this behaviour could also be reproduced using a script
> triggering
> the svn command line client.
> In my opinion, this problem would disappear, when the client side
> sockets
> would be used with the socket option DONT_LINGER or REUSEADDR. Is there
> a technical reason why these options are not used? In other words,
> would it be possible to fix this issue in a future version of the
> subversion libraries.

DONT_LINGER is the default setting if I read the winsock documentation
correctly and REUSEADDR is only valid on incoming connections (which the
client has none).

So, unless your question applies to the server side I think neither of those
settings apply?

> During my research I have found a discussion with the title
> "[Subclipse-dev] Excessive use of TCP sockets" about a similar problem
> on this mailing list, but I was not able to extract a solution for my
> problem.
> Do you have a hint for my problem? At the moment I am using an ugly
> workaroung to prevent this problem (waiting until sockets can be opened
> again).
> If you have further questions, please don't hesitate to ask.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-13 17:12:32 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.