"Alexander Kitaev" <email@example.com> wrote on 02/10/2006 01:05:28 PM:
> > I don't know why it does this, but it does take 10+ minutes
> > on my mac for this to complete. There are over 7,000 files
> > in these subdirectories on my computer.
> > We're using JavaSVN and svn+ssh urls.
> I do not think this is realted to JavaSVN - in my JavaSVN workspace I
> exeprience the same problem - test repositories and working copies of
> tests are created automatically inside the workspace (so far I didn't
> way to create them outside) - so there are a lot of files and small
> copies inside the workspace.
> Sometimes (but not every time), Eclipse decides to refresh these files
> directories and SVNStatusSubscriber takes a lot of time to update svn
> statuses for those files. Sometimes it happens on synchronization and
> sometimes on Eclipse startup (probably after Eclipse crashed or
> with -clean option).
> I think the workaround could be to create temp files outside the
> or somehow configure Subclipse to ignore certain files and directories.
But if Eclipse gives us thousands of files to refresh the status of, even
if we are ignoring them, it is going to take a certain amount of time and
processing just to figure out that they are ignored. That being said,
perhaps there are less expensive ways to reach that decision, but it might
be at the price of making the time to refresh the status of a non-ignored
item take longer.
The real problem is, as you pointed out, that it is not all that easy to
figure out the root trigger of the problem so that you can debug it.
Finally, just to be clear, I do not think what we have been talking about
has anything to do with commit being slow. Just general slowdowns in
Eclipse when this happens.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Feb 10 19:36:29 2006