Denny Valliant <valliant@unm.edu> wrote on 01/31/2006 04:51:16 PM:
> Mark Phippard wrote:
> >
> Might it be possible to only load the SVN Console when there is output
> for it? Instead of right at start up?
> :Denny
I tried variants of that. It turns out the problem has nothing to do with
the Console, that is just where the error manifests. If you remove that,
it just manifested somewhere else. It basically comes down to our plugins
needing to complete their start() method within 5000 ms. I changed
everything I could to be lazy loaded, but in most cases if you have views
open etc.. the code all still gets called right away.
The biggest win I made was that I changed the core plugin to only load
your selected adapter, instead of at the time all 3. When I made the
change that seemed to have fixed the problem. I then noticed it return a
few weeks later, and the only think I could think of that was different
was that I was now using JavaSVN instead of JavaHL. This is what led me
to speculate that maybe JavaSVN takes a little more time to initialize the
adapter than JavaHL does.
The other issue is that the adapter startup code will fallback to JavaSVN
if JavaHL fails to load. So if people never visit their preferences and
specifically select JavaSVN as the adapter, they are likely burning a few
milliseconds at startup as we first try to load JavaHL.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Jan 31 23:05:18 2006