[Subclipse-users] Slow commits due to keep-alive

Hi,

I just upgraded Subclipse to the latest version, and suddenly commits
(and many other requests) are going really slowly.

I have watched the network traffic using ethereal and discovered the
following:

A single socket is be opened and a request sent. This request is
answered immediately:

PUT /txt2/!
svn/wrk/00000109689a6135/branches/james/src/com/pharaohsystems/txt2/photograb/daemon/PhotoGrabberDaemon.java HTTP/1.1
Host: svn.leeds.apnuk.com:80
User-Agent: JavaSVN 1.0.2 (http://tmate.org/svn/)
Keep-Alive:
Connection: TE, Keep-Alive
TE: trailers
Authorization: Basic (etc)
Content-Length: 4398
Accept-Encoding: gzip
Content-Type: application/vnd.svn-svndiff

(etc etc)

HTTP/1.1 204 No Content
Date: Tue, 14 Feb 2006 15:00:08 GMT
Server: Apache/2.0.54 (Debian GNU/Linux) DAV/2 SVN/1.1.4
PHP/5.0.5-Debian-0.8~sarge1
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/plain

This socket will then remain idle for exactly 15 seconds, presumably due
to the keep-alive request, at which point the server sends a FIN and
closes the socket.

Immediately then another socket is opened and the next request sent.
This continues until all requests are complete.

Obviously this is making an operation which should take something like n
x 0.1 seconds take n x 15 seconds, a 150 times increase.

I'm not familiar with the internals of Subclipse so I am not sure if the
problem is likely to lie in that or elsewhere, could someone point me in
the right direction please?

James