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

Re: [Subclipse-users] Calculating Decoration - why so slow?

From: Tom Walter <tom.walter_at_hitwise.com>
Date: Thu, 08 Jan 2009 11:28:24 +1100

I've done as you suggest and timed it. It seems that a manual refresh on
the project (with no modified files) takes about 5 mins, which is the
same length of time as an svn switch or an svn branch/tag. This remains
the same whether I run the refresh immediately prior to the svn switch
or not.

So clearly it is just that eclipse takes a long time to refresh my
particular project. I'll see what I can do about that. I suspect it is
because it is a large project accessed from windows over a samba
connection to a linux fileserver.

I think you've mentioned before that subclipse has to do the full
refresh to ensure eclipse refreshes the hidden .svn directories. It
would be great to see an enhancement to subclipse that could trigger
eclipse to refresh only the files changed by svn (and the hidden .svn
directories), without requiring a full project refresh. I think that
would provide substantial performance increases for people who develop
on remote servers, which is not uncommon. As it is, a 5 minute wait
after any project level svn process makes subclipse impractical for use
in this situation. Can I file a feature request?

Anyway, thanks for taking the time to respond Mark.

Mark Phippard wrote:
> On Mon, Jan 5, 2009 at 12:40 AM, Tom Walter <tom.walter_at_hitwise.com> wrote:
>> I have a project with 10k odd files. When using 'compute deep outgoing
>> state' and doing any non trivial thing like switching branches or
>> opening a new project, the 'SVN Decoration Calculation' task seems to
>> never end. I am not sure if it crashes or what, but generally I get
>> bored and kill the eclipse process after 10 mins or so. Because also
>> when this task is running it prevents other user tasks from occurring.
>> Also occasionally it seems to run out of memory and shut down eclipse at
>> about 1 GB or so.
>> I can get around it by turning off deep outgoing state of course... but
>> this makes it difficult to tell the status of the project... which is a
>> major feature I use from subclipse.
>> Running a command line svn status on the project finishes in
>> milliseconds, so what exactly is taking all the time in eclipse?
>> I am on windows, the files are hosted on a linux machine that I connect
>> to over LAN using samba. Eclipse 3.4.1, Subclipse 1.4.7, using JavaHL.
>> I've tried reinstalling eclipse and subclipse from scratch, and
>> recreating the project, starting with eclipse - clean and all that. I
>> don't think it is a problem with the state of my environment. It seems
>> to be something that subclipse particularly doesn't like about either
>> the files in the project or perhaps the network setup...
>> Any suggestions would be appreciated.
> What happens if you right-click on project and choose the Refresh
> option before you do this? It sounds like your workspace might be out
> of synch.
> The switch option does a refresh after it runs, so if your workspace
> was out of synch, this can take a long time to run. If you do the
> refresh first, that can give you an idea if that is the problem or
> not.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-01-08 01:28:53 CET

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.