Bug 135146 - rcp.performance.EmptyWorkbenchPerfTest#testOpen() runs too fast
Summary: rcp.performance.EmptyWorkbenchPerfTest#testOpen() runs too fast
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 RC2   Edit
Assignee: Shaun Skelton CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2006-04-05 16:44 EDT by Tod Creasey CLA
Modified: 2006-07-13 12:00 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 2006-04-05 16:44:29 EDT 
M6

rcp.performance.EmptyWorkbenchPerfTest#testOpen() as do most of the other associated tests
Comment 1 Tod Creasey CLA 2006-04-18 09:22:26 EDT 
Times are good now
Comment 2 Karice McIntyre CLA 2006-05-12 10:40:04 EDT 
Checked RC3 performance tests results.  The following 2 tests run in well less than 100 ms:
rcp.performance.EmptyWorkbenchPerfTest#testRestore() [close]
rcp.performance.EmptyWorkbenchPerfTest#testOpen() [close]

Is this ok?
Comment 3 Tod Creasey CLA 2006-05-12 11:07:02 EDT 
How much is well under? The answer is no - we should try for 100ms minimum
Comment 4 Karice McIntyre CLA 2006-07-13 11:59:18 EDT 
bug 116284 and bug 116282 cover the problems with the rcp tests running too slow.
Comment 5 Karice McIntyre CLA 2006-07-13 12:00:50 EDT 
d'oh - i meant to say those rcp tests were running too fast, not too slow!