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

Re: [Subclipse-users] Eclipse + Subclipse - 3500 files - file save very slow

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 16 Apr 2008 13:35:01 -0400

On Wed, Apr 16, 2008 at 1:21 PM, Christopher Lang
<christopher.lang_at_acurana.de> wrote:

> I did some more research on that issue. In the past I had the project folder
> (in ~./workspace/..) renamed. In order for Eclipse to still be able to access
> the project folder under the old name I added a symlink with the original
> folder name, pointing to the renamed folder.
> This works in general, but seems to *cause* the long delays when saving a
> file.
> Maybe this can be fixed in subclipse, though I am not sure if it is worth it.

If you use JavaHL, it can manage the working copy being a symlink much
faster than SVNKit. That being said, Eclipse can just point at a
project in any location on your drive, so you should not really need
to use a symlink for this. Projects do not have to be located in the
workspace folder.

> > Do you do your builds outside of Eclipse?
> yes, sometimes, but the 'build' directory is properly added to svn:ignore and
> does not cause any problems.

It can still cause a performance problem. Even though the files will
be ignored, Eclipse does not ignore them. If a refresh is triggered,
it will refresh its internal cache of those files as well as flood the
pipeline with resource change events. Subclipse has to process each of
these and determine that the file is ignored. This sort of thing can
easily eat up 5 seconds of time. You should be able to rule this out
simply by right-clicking on the project and using the Refresh option
prior to editing the file.

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-04-16 19:35:09 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.