Bug 112927 - [performance] Update CVS workspace job takes too long
Summary: [performance] Update CVS workspace job takes too long
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P1 normal (vote)
Target Milestone: 3.2 RC1   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
: 119848 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-10-18 09:55 EDT by Olivier Thomann CLA
Modified: 2006-04-25 14:01 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Thomann CLA 2005-10-18 09:55:04 EDT 
When starting the workspace in the morning, as soon as I switch to the
Synchronize view it takes about 10 minutes to complete the job "Updating CVS
Workspace". If I kill it, I can immediately see exactly the outgoing changes.
Indeed I need to kill it to start a "Synchronize" with the repository in order
to get latest incoming changes.
In my workspace I have:
org.eclipse.jdt.ui
org.eclipse.jdt.ui.tests
org.eclipse.jdt.ui.tests.refactoring
org.eclipse.jdt.core
org.eclipse.jdt.core.tests
org.eclipse.jdt.core.tests.builder
org.eclipse.jdt.core.tests.compiler
org.eclipse.jdt.core.tests.model
org.eclipse.jdt.core.tests.performance
jdt-core-home
jdt-core-www
org.eclipse.releng
org.eclipse.test.performance.win32
org.eclipse.test.performance

from source and shared with a CVS repository.
Comment 1 Michael Valenta CLA 2005-12-14 10:24:41 EST 
*** Bug 119848 has been marked as a duplicate of this bug. ***
Comment 2 Michael Valenta CLA 2006-03-30 09:33:26 EST 
I have come up with a nice way to deal with this but it requires API to be added to an exisiting class. I need the class SynchronizationContext to extend PlatformObject so I can get access to an internal background handler. This will allow me to track the state of the handler and show an appropriate message in the sync view. With this, on startup, the view will display that it has yet to be initializaed. Then the user can choose to initialize or sync and the view will be populated.

McQ, can I get approval for the API change? I can get it into M6 since we will need a rebuild to deal with the ISaveable changes anyway. I will then be able to implement the above described behavior early in RC1.
Comment 3 Olivier Thomann CLA 2006-03-30 09:38:01 EST 
This would definitely be a plus for the out-of-the-box experience.
Right now it takes a long time after each restart to update the cvs information.  This is blocking other possible cvs operations and it slows down the start of the java tooling.
Comment 4 Mike Wilson CLA 2006-03-30 09:45:11 EST 
+1. go for it.
Comment 5 Michael Valenta CLA 2006-04-04 16:13:47 EDT 
Fix released to HEAD
Comment 6 Michael Valenta CLA 2006-04-25 14:01:37 EDT 
Verified