Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Dali Profiling"
(New page: == CPU Performance == * [http://java.dzone.com/articles/best-kept-secret-jdk-visualvm Java VisualVM ] ** jvisualvm.exe found in the bin folder of the JDK (JDK 1.6 update 7 or greater) ==...) |
(→CPU Performance) |
||
| Line 1: | Line 1: | ||
== CPU Performance == | == CPU Performance == | ||
* [http://java.dzone.com/articles/best-kept-secret-jdk-visualvm Java VisualVM ] | * [http://java.dzone.com/articles/best-kept-secret-jdk-visualvm Java VisualVM ] | ||
| − | ** jvisualvm.exe found in the bin folder of the JDK | + | ** Run jvisualvm.exe found in the bin folder of the JDK (JDK 6 update 7 or greater) |
| + | |||
| + | === Dali Specific Settings === | ||
| + | These are starting points for which classes to profile, it at least narrows things down so that the profiler can finish without using up too much memory or just taking too long. Add more packages to profile as necessary. | ||
| + | |||
| + | check 'Settings' check box: | ||
| + | |||
| + | * Start profiling from classes: | ||
| + | ** org.eclipse.jpt.** | ||
| + | |||
| + | * Profile only classes: | ||
| + | ** org.eclipse.jpt.** | ||
| + | |||
| + | |||
| + | === Eclipse Platform Settings === | ||
| + | check 'Settings' check box: | ||
| + | |||
| + | * Start profiling from classes: | ||
| + | ** org.eclipse.ui.** (or org.eclipse.e4.**) | ||
| + | |||
| + | * Profile only classes: | ||
| + | ** org.eclipse.e4.* | ||
| + | ** org.eclipse.ui.* | ||
| + | ** org.eclipse.core.* | ||
| + | ** org.eclipse.jface.* | ||
| + | ** org.eclipse.swt.* | ||
== Memory Performance == | == Memory Performance == | ||
Revision as of 14:42, 25 February 2013
Contents
CPU Performance
- Java VisualVM
- Run jvisualvm.exe found in the bin folder of the JDK (JDK 6 update 7 or greater)
Dali Specific Settings
These are starting points for which classes to profile, it at least narrows things down so that the profiler can finish without using up too much memory or just taking too long. Add more packages to profile as necessary.
check 'Settings' check box:
- Start profiling from classes:
- org.eclipse.jpt.**
- Profile only classes:
- org.eclipse.jpt.**
Eclipse Platform Settings
check 'Settings' check box:
- Start profiling from classes:
- org.eclipse.ui.** (or org.eclipse.e4.**)
- Profile only classes:
- org.eclipse.e4.*
- org.eclipse.ui.*
- org.eclipse.core.*
- org.eclipse.jface.*
- org.eclipse.swt.*
Memory Performance
SWT/Handles
"No more handles"