Re: [Subclipse-users] Slowness in svn+ssh

> I cannot imagine Eclipse overhead is 11 minutes. Assuming this is
> a Java
> project there should be some compiling to do. You should be able
> to get
> an idea on the Eclipse overhead by watching the SVN Console and seeing
> when the checkout finishes. Keep in mind that Subclipse also needs
> to do
> a full status crawl of the files which can take a little while. I
> would
> not expect it to be this great. Maybe 3-4 minutes total but not
> 12. If
> it is not too hard to setup http:// you could try that. Maybe
> JavaSVN is
> experiencing some kind of problems with your SSH Server? Typically
> JavaSVN is a little faster than JavaHL.

The checkout itself does not finish until about 11m45s (i.e. the
console says its updating files until that time). Then there is
another 30s of just sitting with no console action while it "crawls"
the files likely. I am trying to see what the feasibility of
installing as an Apache module (http://) or running the daemon
(svn://) is sometime in the future.

> What have you tried? If you have the command line working, and you
> have
> the JavaHL binaries I would almost expect it to just work. JavaHL
> will
> not prompt you for credentials, so you need to be using some kind of
> key-agent, but most SSH users already do. I think if you launch
> Eclipse
> from a Terminal session then it ssh will prompt you for info as needed
> within that session.

I have not tried setting up the config files to do all the necessary
ssh auth yet, but I will. I'll definitely try that trick about
launching from within terminal. I had no idea it would prompt me like
that.

> It would be worth seeing how long it takes to do File -> Import of an
> existing project. That would give an idea as to how much the combined
> Eclipse/Subclipse overhead should be.

I will also try this and see if the combined time is a lot less than
12min. I suspect it will be. Honstly, I hope its some problem with
JavaSVN connecting to my ssh server because its likely that we won't
be able to switch to using apache or svnserve as a daemon for some time.

I'll keep this thread open with more information as I get it.

Thanks guys,
Bradley

On May 3, 2006, at 3:14 PM, Mark Phippard wrote:

> Bradley Wagner <bradley.wagner@hannonhill.com> wrote on 05/03/2006
> 03:05:26 PM:
>
>> I tried the build with the "-Djavasvn.symlinks=false" system property
>> set in my eclipse.ini file which contains the vmargs for Eclipse on
>> OS X. There was no improvement, checkout still took ~12 minutes.
>>
>> Next, I tried checking out the latest from the JavaSVN trunk and
>> deploying the javasvn.jar and ganymed.jar lib files to the Eclipse
>> directory. The same checkout took ~12 min again. This just seems
>> really slow compared to doing the checkout from the command line
>> using the native HL libraries (1 min). How much of this is just
>> Eclipse overhead and how much of this do you think is JavaSVN?
>
> I cannot imagine Eclipse overhead is 11 minutes. Assuming this is
> a Java
> project there should be some compiling to do. You should be able
> to get
> an idea on the Eclipse overhead by watching the SVN Console and seeing
> when the checkout finishes. Keep in mind that Subclipse also needs
> to do
> a full status crawl of the files which can take a little while. I
> would
> not expect it to be this great. Maybe 3-4 minutes total but not
> 12. If
> it is not too hard to setup http:// you could try that. Maybe
> JavaSVN is
> experiencing some kind of problems with your SSH Server? Typically
> JavaSVN is a little faster than JavaHL.
>
>> Have
>> you ever gotten svn+ssh to work with JavaHL? I'd like to try the same
>> checkout with JavaHL in Eclipse and see what kind of times I get.
>
> What have you tried? If you have the command line working, and you
> have
> the JavaHL binaries I would almost expect it to just work. JavaHL
> will
> not prompt you for credentials, so you need to be using some kind of
> key-agent, but most SSH users already do. I think if you launch
> Eclipse
> from a Terminal session then it ssh will prompt you for info as needed
> within that session.
>
>> It seems like it might be best to just check out the project from the
>> command line and open it in Eclipse, though it is a bit roundabout.
>
> It would be worth seeing how long it takes to do File -> Import of an
> existing project. That would give an idea as to how much the combined
> Eclipse/Subclipse overhead should be.
>
> 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
>

--
Bradley Mitchell Wagner
Software Developer
Hannon Hill Corporation
main: (678) 904-6900 ext. 115
email: bradley.wagner@hannonhill.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org