Bug 101072 - [Presentations] Presentation performance suites failing
Summary: [Presentations] Presentation performance suites failing
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks: 100805
  Show dependency tree
 
Reported: 2005-06-21 11:41 EDT by Tod Creasey CLA
Modified: 2019-09-06 16:15 EDT (History)
1 user (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 Tod Creasey CLA 2005-06-21 11:41:40 EDT 
RC3

http://fullmoon.ottawa.ibm.com/eclipse/downloads/drops/S-3.1RC3-200506171618/performance/org.eclipse.ui.php?

The presentation suites are showing that presentations are consistenly sloweer
in 3.1.

The R21 presenations in particular are performing poorly although the
WorkbenchPresentationFactory has the odd failure here and there are well.
Comment 1 Tod Creasey CLA 2005-06-21 12:35:35 EDT 
As these are mostly in the 2.1 presentation it was decided that this is not a
prioirity for 3.1.
Comment 2 Michael Van Meekeren CLA 2005-06-21 13:11:11 EDT 
TC, the link points to fullmoon, is this server (the one that does the eclipse
builds before sending them to the eclipse server) visible outside IBM?

If not I guess users can go to the download for 3.1RC3 and select the
"Performance Results" link on the top.
Comment 3 Tod Creasey CLA 2005-06-21 13:51:51 EDT 
That is the link on the webpage currently but others can follow your method
Comment 4 Paul Webster CLA 2006-09-28 15:15:12 EDT 
Is this still a problem in 3.3?

PW
Comment 5 Denis Roy CLA 2007-06-22 09:33:01 EDT 
Changes requested on bug 193523
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:15:17 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.