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

Re: [Subclipse-users] JavaHLConnector creates a huge amount of short living threads

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 4 Jun 2008 15:44:10 -0400

On Wed, Jun 4, 2008 at 7:09 AM, Micha Riser <mr_at_carrara.ch> wrote:
> Whenever I start eclipse with all my svn projects, there are more than
> 1000 threads created by the JavaHLConnector! This degrades performance
> and I have to wait about half a minute until the svn overlays show up
> and eclipse is finally usable. I tracked the issue and noticed that in
> JavaHLConnector, a new thread is created with each new
> ProcessMonitorWrapper. It is much more efficient to use only one thread
> to monitor all process monitors!
> I have made a patch where one thread as singleton watches all progress
> monitors for cancellation. For me this improved the startup speed of
> eclpse considerably. This thread stays running all the time (blocked on
> a monitor if it has nothing to do), but could also be killed when it
> has no more things to watch by adding a timeout to the wait().
> Same issue concerns the svnkit connector implementation.
> Please consider fixing this issue.

I thought this message referred to a lot of things I did not know what
you were talking about. When I opened the patch, I knew why. Your
patch is for Subversive. This is Subclipse.

Mark Phippard
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-06-04 21:44:20 CEST

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

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