PEtALS 2.0 & pack (2007/09/28)| Chapter 7. Profiling with PEtALS | ||
|---|---|---|
 |  | |
Table of Contents
This chapter describes how to profile a PEtALS instance. You could profile a PEtALS instance to optimize the NMR, components or services.
This chapter describes how to profile a PEtALS instance using NetBeans 5.5.1.
Download the profiler remote pack corrsponding to your system,
Unpack the downloaded archive on remote machine:
mkdir nb-profiler-server cd nb-profiler-server unzip ../profiler-server-551-linux-15.zip
Run the calibration:
cd bin ./calibrate.sh
Start NetBeans IDE
Launch the attach profiler wizard (menu Profile/Attach Profiler...), select "Analyze Performance":
Select "Entire Application" and "Exclude Java Core Classes". Click on "Customize Filter":
To defined a PEtALS global filter, click on "Edit Global Filters":
Click on "New" to add the PEtALS global filter:
Click on "Edit" to defined filter:
Set the value to: "org.objectweb.petals.", don't forget the last dot.
Click on "OK" to save the new global filter.
Click on "Add" to define a new filter set:
Set its name to "Exclude extra classes for PEtALS", set its type to "Exclusive", and select the following filters:
Apache.org classes,
W3C.org classes,
XML.org classes
Click on "Add" to define a new filter set:
Set its name to "Include PEtALS classes", set its type to "Inclusive", and select the filter "PEtALS classes".
Click on "OK" to save the configuration.
Click on "Attach Wizard" to defined the remote PEtALS instance:
Select "Application", and click on "Next":
Select "Remote", and set the correct values in fields "Hostname" and "Host OS", and click "Next":
Click on "Finish".
Click on "Attach" to start the profiling.
Now, you can play with PEtALS.
| | | |
| Chapter 6. Remote debugging with PEtALS |  | Chapter 8. Best practices |