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

Re: [Subclipse-users] Slowness on Checkout, Synchronize

From: Andrew Goodnough <Andrew.Goodnough_at_wicourts.gov>
Date: 2006-04-13 20:04:42 CEST

>>> On Thu, Apr 13, 2006 at 11:03 am, in message
<OF88C37503.2E8D4128-ON8525714F.0057BC21-8525714F.00589CC0@softlanding.com>,
Mark Phippard <markp@softlanding.com> wrote:
> "Andrew Goodnough" <Andrew.Goodnough@wicourts.gov> wrote on
04/13/2006
> 11:42:37 AM:
>
>> We're authenicating to an LDAP server thru Apache WebDAV. Apache
and
>> SVN are on the same SUSE Linux box. The CLI is very quick on all
>> operations so we think this is a problem at the Subclipse level.
>> Checking out one of our applications is also slow from Subclipse
and
>> takes 11.5 min every time. I've been told it's a large project by
SVN
>> standards - 20046 items, totalling 239.5 MB. It also was brought
over
>> with 4- 5 years of history (branches/tags, everything) from CVS
using
>> cvs2svn.
>>
>> Things we've tried to fix it, nothing worked except #3 and we don't
>> want to do that:
>> 1) Turning off indexing of the drive on Windows clients
>> 2) Switching the Subclipse preferences to use JavaHL instead of
>> JavaSVN.
>> 3) Using SSH (we don't really want to lose the LDAP auth, though)
>> 4) Looking through the Subclipse code. I noticed that most of the
core
>> methods in the JavaSVN code (checkout, update) are synchronized.
My
>> theory was that it was the synchronized Java wrapper around the
"fast" C
>> libraries that was slowing things down. But, if this is true, using
the
>> JavaHL setting should have bypassed these methods and made them
faster,
>> which it didn't.
>>
>> Thanks in advance for any ideas.
>
> I would guess that the Eclipse build and Subclipse status crawl would
add
> a lot to the slowness. An SVN command line checkout does not do
either of
> these. The console view should reflect this as you should be able to
see
> when the checkout stops.
>
> snip
>
> Mark

We've tried turning off automatic building in Eclipse to no effect.
What do you mean by a "status crawl"? I'm assuming you mean an 'svn
status' type of operation at the project level. I can see where this is
unavoidably resource intensive (because every file must be visited).
Also, does the Team->Compare With->Base revision use the local copy of
the pristine server version at the last checkout? or does it, too, have
to make a trip to the server?

Andy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Apr 13 21:23:44 2006

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.