Bug 149158 - [performance] Opening the RSE Perspective for the first time is slow
Summary: [performance] Opening the RSE Perspective for the first time is slow
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.0   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2006-06-29 10:06 EDT by Martin Oberhuber CLA
Modified: 2008-08-13 13:05 EDT (History)
0 users

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 Martin Oberhuber CLA 2006-06-29 10:06:46 EDT 
Opening the RSE Perspective for the first time is very slow.
Startup performance should be improved.
Comment 1 Martin Oberhuber CLA 2006-08-10 11:16:02 EDT 
Increasing priority and reassigning to DKM since the slow startup of the RSE Perspective is a show-stopper for products including the RSE.

To be clear, after Launching Eclipse, opening the RSE perspective takes about 20 seconds even on a very fast computer. This happens whenever Eclipse is started (not just the first time).

See also bug 153446 (deleting connections is slow), perhaps the problem is in the DOM.
Comment 2 David McKnight CLA 2006-08-10 11:59:16 EDT 
I tried to reproduce this but it's fast for me.  Is it possible that some other plugins like maybe service discovery is slowing this down?
Comment 3 Martin Oberhuber CLA 2006-08-10 12:24:42 EDT 
Hmm, I also cannot reproduce the extreme delays any more. 

Some measurements:
* Open CVS Repository Explorer Perspective - 2 sec.
* Open RSE Perspective - 4 sec (consistently, regardless of #connections).

It's still perceived slow but probably reasonable. I think it would be a good idea to investigate, but I'm reducing priority for now.
Comment 4 Martin Oberhuber CLA 2006-08-21 07:44:02 EDT 
With Eclipse 3.2 release / RSE 1.0 M4, no excessive delays are visible any more.
Supposedly, this was caused due to lots of debug prints.

Test cases should cover cases with large DOMs though.
Comment 5 Martin Oberhuber CLA 2008-08-13 13:05:52 EDT 
[target cleanup] 1.0 M4 was the original target milestone for this bug