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

Re: [Subclipse-users] Commiting takes forever: retrieving svn synchronization data

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-02-27 15:47:39 CET

On 2/27/07, Eric Kobrin <ekobrin@ediets.com> wrote:
>
> After doing a one-file commit, subclipse spent over six minutes
> "retrieving svn synchronization data." This seems a little excessive. Doing
> a single-file commit from the command line took five seconds as measured
> with the time utility under cygwin.
>
>
>
> The branch in which I am working contains over 20,000 files distributed
> through many subdirectories.
>
>
>
> This is on subclipse version 1.0.5
>
> Using svn:// paths
>
> Using JavaHL
>
> Running on Eclipse version 3.2.1
>
> On Windows XP with fast indexing turned off for the working copy
> directory.
>
You should be using Subclipse 1.2.0 (although I am not saying it will make a
difference). When you do a commit from the Synchronize view, the
Synchronize option is re-run/refreshed after the commit. That is what it is
taking 6 minutes. This is necessary to insure accurate data in that view.
If it did not do this, and you committed before you did an update, then when
you did the update we would update to an older revision which, depending on
the context you chose to update, would remove your commit from the
workspace.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on Tue Feb 27 15:47:54 2007

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.