On Mon, Aug 18, 2008 at 12:07 PM, Kyle Mahan <kyle.mahan_at_gmail.com> wrote:
> I'm running Eclipse 3.4 and Subclipse 1.4.3 (in Windows) and have recently
> started noticing some weird slow-downs -- mainly with synchronization (like,
> I always ended up killing it after 5-10 minutes), but also it was taking a
> long time (maybe 10-20 seconds) for the popup menu to come up after
> right-clicking an SVN project, and various other operations were slower than
> they should have been. I had tried SVNKit with both password and private key
> authentication and also JavaHL with TortoisePlink, and both had pretty much
> the same result. I'm fairly confident that the latter is configured
> correctly because command line and Tortoise work with no problem.
>
> While I was using JavaHL, I noticed that Eclipse was kicking off a lot of
> TortoisePlinks during a synchronize, sometimes 4-5 at a time. They would
> spawn and then die immediately, which didn't seem right, so I decided to try
> manually port-forwarding with PuTTY and using svn://localhost instead. And
> lo and behold, synch happens nearly immediately now. So I assume that
> starting a new plink for each svn status and info was what caused it to be
> so slow--has anyone else had this problem? Any idea how to fix it?
It is not in the power of Subclipse to fix this. The connection
management all lives within the Subversion API. I'd assume you would
get a boost by using SVNKit, as I thought they maintained a persistent
SSH connection that they reused. You could ask support_at_svnkit.com if
this is still true or if there are options for it. Perhaps they had
to make it more like Subversion native to fix a problem?
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-18 18:11:21 CEST