Community
Participate
Working Groups
Add support for monitoring performance and detecting problems in performance critical aspects of the Eclipse Platform. Potential critical areas to monitor include the times to: start up a plug-in, open an editor, display a menu, switch perspectives, process an SWT event, process a resource change event, etc. [Platform UI; Platform Core; SWT]
*** Bug 76807 has been marked as a duplicate of this bug. ***
We have now hooked up the core runtime performance work to the UI Stats. If you look in the .options file of org.eclipse.ui you will see the numbers we have defined for thresholds - feel free to adjust as you see fit for your own use. Currently these events are only collected when the debug flag in the org.eclipse.ui.options is on to reduce the amount of information currently being sent to the log. John is working on a performance log. When this is ready we will turn on this support by default. I have also released the performance view to the basic group which is essentially the core performance spy cut down to only show the performance errors.
We have added performance testing in the following areas: public static final int CREATE_PART = 0; public static final int CREATE_PART_CONTROL = 1; public static final int INIT_PART = 2; public static final int CREATE_PERSPECTIVE = 3; public static final int RESTORE_WORKBENCH = 4; public static final int START_WORKBENCH = 5; public static final int CREATE_PART_INPUT = 6; public static final int ACTIVATE_PART = 7; public static final int BRING_PART_TO_TOP = 8; public static final int NOTIFY_PART_LISTENERS = 9; public static final int SWITCH_PERSPECTIVE = 10; public static final int NOTIFY_PAGE_LISTENERS = 11; public static final int NOTIFY_PERSPECTIVE_LISTENERS = 12; public static final int UI_JOB = 13; public static final int CONTENT_TYPE_LOOKUP = 14;
Verified in 20050510