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

Re: [Subclipse-users] Extremely slow performance in Subclipse method StatusCacheManager.basicGetStatus()

From: jcompagner <jcompagner_at_gmail.com>
Date: Sun, 1 Mar 2009 00:16:56 +0100

On Sat, Feb 28, 2009 at 21:14, Mark Phippard <markphip_at_gmail.com> wrote:

> This can cause performance problems as the build creates a ton
> of new files that Eclipse does not know about. When the workspace
> refreshes and it discovers them it sends a flood of resource changes
> through the system and it can take a while to process all of those.
> We've done most of the optimizations we can, I actually thought the
> problem was resolved as I do not recall hearing it lately

this will always be a problem in the subclipse (or any other subversion
plugin that relies on none eclipse code that takes care of file updates)

it is a bit of a problem that when using subclipse refresh of the
workspace/project/files are done when you execute svn calls.

We already have programmed around that in eclipse in our eclipse product.
Because those refreshes are completely circumventing the workspace
jobs/rules :(
(you get resource/file changes when you dont expect them to happen)

I know that this is just the way it is and that it only really can be fixed
when using svnkit (and never with javahl).
If svnkit would use a file abstraction layer instead of directly files..


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-03-01 00:17:10 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.