Bug 114320 - Investigate performance depreciation in opening GEF editor
Summary: Investigate performance depreciation in opening GEF editor
Status: RESOLVED FIXED
Alias: None
Product: GEF
Classification: Tools
Component: GEF-Legacy GEF (MVC) (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.2.0 (Callisto) M4   Edit
Assignee: Pratik Shah CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-10-30 19:13 EST by Pratik Shah CLA
Modified: 2006-01-23 18:32 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pratik Shah CLA 2005-10-30 19:13:49 EST
Opening the logic editor has slowed down considerably in 3.2 builds as 
compared to 3.1, as is shown here:

http://download.eclipse.org/tools/gef/downloads/drops/I-I20051027-
200510271321/performance/org.eclipse.gef.php

The logic editor uses anti-aliased connections which requires Cairo.  Since 
there is no such problem on Windows, this could be because Eclipse 3.2 uses 
Cairo 1.0, whereas 3.1 used Cairo 0.4.  However, I couldn't reproduce the 
problem with my initial, crude SWT snippet that just drew anti-aliased 
polylines.
Comment 1 Pratik Shah CLA 2005-12-20 14:41:36 EST
This happens on Windows as well.  It's dependent on the state of the test machine's screen.  I haven't seen exactly how all states affect things, but having the screen blanked out certainly improves the results.  Now I don't have any screensavers or screen-blanking and the results are consistent.  To get rid of the misleading drop in performance, we'd have to re-run the 3.1 tests.
Comment 2 Pratik Shah CLA 2006-01-23 18:32:27 EST
Now that the tests are moving to a new machine, they'll be re-run.  Marking as fixed.