On Tue, 30 Nov 2004 14:44:32 -0800, Garrick Olson
> It appears the TortoiseSVN client opens connections to the server, and
> holds them open until the user closes TortoiseSVN.
> Here is the recipe:
> 1. Right click on a working copy, and select TortoiseSVN --> Show Log
> 2. I now see two connections established with the server
> - Sometimes I see only one connection at this point
> - If I stop at this point, it appears the connections remain
The first connection is to fetch the HEAD revision. Then the next
connection fetches the actual log.
> 3. Select a revision, and double click on one of the files modified (to
> open diff tool)
> 4. I now see two *additional* connections established with the server
> (total of four)
> 5. Close the diff tool
> 6. Notice no connections are closed (still four connections established)
> 7. Repeat steps 4 & 5 to create as many established connections as you
> 8. Close the log window
> 9. I now see all connections get closed
> These connections tend to pile up on the server, and seem to consume
> quite a bit of memory. With a large team, the server eventually runs out
> of resources and starts failing to service clients.
Hmmm - I can't see that happening here. But maybe that's because I'm
using http instead of svn://. When I use a port connection tool to
check the open connections, there are sometimes two or three
connections listed, but only one of them is really 'open' - the others
are in state wait_close which means they're closed by the client and
wait for ack of the server.
Are you sure that those connections really are open? There was a
problem like that in earlier versions of TSVN, but now I'm using a
local pool for all Subversion commands which gets destroyed after each
command. And of course, the connection is closed when the local pool
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Dec 1 11:14:31 2004