Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 76807 - Performance threshold enforcement
Summary: Performance threshold enforcement
Status: RESOLVED DUPLICATE of bug 80138
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-22 09:56 EDT by John Arthorne CLA
Modified: 2004-12-06 14:20 EST (History)
3 users (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 John Arthorne CLA 2004-10-22 09:56:09 EDT 
Various plugins have tracing options to record the time for running things like
builders, opening editors and views, etc. To take an extra step, we should add
acceptable threshold levels, configurable from an option file. An error would be
written to the log (or a separate performance log) when the acceptable threshold
value is exceeded. This "performance testing" mode would also be enabled with a
debug option so it doesn't impact runtime performance for end users.

This requires work across many components, but runtime support could be added to
ensure a uniform approach.
Comment 1 John Arthorne CLA 2004-12-06 14:20:26 EST 
This was recently added to the 3.1 plan. Marking as a duplicate of the plan item.

*** This bug has been marked as a duplicate of 80138 ***