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

Re: [Subclipse-dev] Excessive use of TCP sockets

From: Thomas Hallgren <thomas_at_tada.se>
Date: 2007-06-14 22:29:09 CEST

Hi Karen,

Karen Tracey wrote:
> Excuse me butting in, but what really is the problem here?
This is the problem: https://bugs.eclipse.org/bugs/show_bug.cgi?id=192385

If all users opens hundreds (or even thousands) of sockets each time
they use our tool, I think there is a high risk that many servers reach
a limit where they start refusing connections before the tool has
completed its task.

> So >100 connections in TIME_WAIT is not a problem unless you believe
> that whatever the application was doing shouldn't have required >100
> individual connections in the first place. I know nothing of the code
> involved here but it seems possible that each call to
> getList/getContent/getDirEntry would use its own TCP connection, thus
> if you make 100+ calls you might wind up with about that many
> connections lingering in TIME_WAIT for a bit. Unless you think that
> many connections should NOT have been required for the calls made,
> then I don't see the problem here.
I compare with CVS where only one connection is established between the
client and the server and all commands reuse that single connection. I
have no idea how the client/server protocol is set up in SVN but if each
command opens a socket of its own, then I might have a big problem. We
potentially execute thousands of such commands in a fairly short time frame.

- thomas

To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Thu Jun 14 22:29:55 2007

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

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