Documentation generated
from the Eclipse Help
for the product
Setting Up Launch Configuration
To run an application
with the CodePro Profiler, you need to create corresponding launch
configuration. This can be done using the same methods for
creating Run and Debug launch configurations.
Using Profile With CodePro As context
menu in the Package Explorer.
Using the drop-down menu of the Profile toolbar
action.
Use
Open Profile Dialog... to manage profile mode
launch configurations.
Types of supported launch configuration are:
Java application
Java applet
Unit test suite
Eclipse application
CodePro Profiler adds a Profiling tab to the set of standard launch configuration tabs.
Launch Configuration Settings:
CPU Settings - Profiling Types:
Telemetry only
CPU sampling - Specify the time interval between two metering for sampling process.
Byte Code Instrumentation (BCI).
Instrumentation filters (only for BCI)
Choose
the set of packages and classes which shouldn't be instrumented using Add Filter and the set of exclusions from the previous set using Add
Exclusive Filter....
Command
Action
Add Filter
Adds a new filter to the set of BCI filters.
Add Exclusive Filter...
Adds an exclusion to action of the filter. Example:
Filter: "java.*". Exclusive filter: "java.lang.*". Result:
"java.lang.*" methods will be instrumented, all other "java.*" methods
will not.
Change Filter...
Allows changing the selected filter.
Delete Selected Filter
Deletes the selected filter.
Clear
Clears the list of BCI filters.
Restore Defaults
Restores a set of BCI filters to the default settings.
Memory Profiling Settings (Applies to BCI profiling type only)
Track allocation objects This option allows recording of object allocations.
Collect object lifetime information This option allows lifetime profiling.
Thread Profiling Settings:
Enable thread profiling. This option allows thread profiling.
Telemetry Settings:
Telemetry interval. Specify the time interval between two telemetry metering.
Actions on Exit:
Take snapshot on exit. This option allows taking CPU, memory or both snapshots on exit of application.