Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342333 - Enhance PerformanceStats so that it can be used by more groups
Summary: Enhance PerformanceStats so that it can be used by more groups
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.6.2   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-08 16:26 EDT by Gary Karasiuk CLA
Modified: 2019-11-14 02:24 EST (History)
0 users

See Also:


Attachments
A patch to provide for alternative implementations of PerformanceStats (6.18 KB, patch)
2011-04-08 16:28 EDT, Gary Karasiuk CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Karasiuk CLA 2011-04-08 16:26:59 EDT
It is great that the runtime includes the PerformanceStats class, but I would like to open this up so that more groups can use it.

Today I can override the implementation of the org.eclipse.test.internal.performance.PerformanceMeterFactory I would like so be able to do something similar with the PerformanceStats class.

I have attached a small patch, that provides this function. 

The motivation behind this, is so that adopting products (including WTP) can instrument their code with startRun() and endRun(), and then performance teams can intercept those calls and do detailed performance measurements.
Comment 1 Gary Karasiuk CLA 2011-04-08 16:28:30 EDT
Created attachment 192880 [details]
A patch to provide for alternative implementations of PerformanceStats
Comment 2 Lars Vogel CLA 2019-11-14 02:24:26 EST
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.