Bug 253757 - Performance Suite generator
Summary: Performance Suite generator
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-04 13:16 EST by Paul Webster CLA
Modified: 2019-09-06 16:12 EDT (History)
4 users (show)

See Also:

Attachments
Perf results v01 (11.55 KB, patch)
2008-11-04 13:34 EST, Paul Webster CLA 		no flags Details | Diff
Example results comparison (31.40 KB, text/html)
2008-11-04 13:35 EST, Paul Webster CLA 		no flags Details
View All 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 Paul Webster CLA 2008-11-04 13:16:07 EST 
A place for performance suite patches.  It includes updating the org.eclipse.test.performance to write out a TAB separated file and a small tool to turn 2 files (baseline and performanceRun) into an HTML file to compare elapsed times.

PW
Comment 1 Paul Webster CLA 2008-11-04 13:34:41 EST 
Created attachment 116986 [details]
Perf results v01

This changes the InternalPerformanceMonitor to output a TAB separated file, by default in the org.eclipse.ui.tests.performance directory.  The launch config will run in the 3.5 branch.  The GenHtml launch config requires you to select 2 files, baseline and the performance run, and then generates results in $HOME/perf_run.html

This patch could be applied to the 33x baseline, but the launch configs need to be updated to say -Dperf.branch=33x instead of 350

PW
Comment 2 Paul Webster CLA 2008-11-04 13:35:25 EST 
Created attachment 116987 [details]
Example results comparison
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:12:42 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.