Hi,
The proposed cleanup did not help.
I manually committed everything, deleted the project in Eclipse and did a
fresh checkout.
That fixed the issue.
Thanks for the hints!
cheers
Chris
Am Montag 14 April 2008 14:42:26 schrieben Sie:
> On Mon, Apr 14, 2008 at 6:19 AM, Christopher Lang
>
> <christopher.lang_at_acurana.de> wrote:
> > When subclipse is active file save is very slow. It takes about 2-5 sec.
> > on every file save.
> >
> > Is there a workaround, like for example a setting which disables
> > subclipse file tree update on every file save?
>
> That does not sound normal. I can think of a couple things to try.
>
> 1) Do Team > Cleanup on the project. Subversion stores the file
> date/time in its metadata. If all of your files had their date/time
> modified, but not their content, then this will cause Subversion to do
> full byte by byte comparisons on each file which will make the process
> take longer. Among the things that Cleanup does, is updating this
> metadata with the current date/time stamp. The command does not
> produce any output. Just run it and then edit and save a file to see
> if there is a difference. Doing an Eclipse refresh of the project
> after you run Cleanup would not be a bad idea either.
>
> 2) Do you have hundreds or thousands of files in the same folder.
> Perhaps your C build output is also in the same folder as the source?
> If this is the case, then it might be taking Subversion an unusually
> long time to refresh the status on the file.
---------------------------------------------------------------------
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-15 15:52:25 CEST