Current Page:
NeXtMidas Training
NetBeans - Part 3 (Profiler)
Profiler Setup
Step 11
|
+ Start Here
+ Background
+ Common Midas Concepts
+ Getting Started - Part 1
+ Getting Started - Part 2
+ Working with Files
+ Option Trees
+ Macros - Part 1 (Basics)
+ Macros - Part 2 (Graphics)
+ Primitives
+ NetBeans - Part 1 (Setup)
+ NetBeans - Part 2 (GUIs)
- NetBeans - Part 3 (Profiler)
+ About Profilers
- Profiler Setup
- Calibration
- Step 1
- Step 2
- Step 3
- Step 4
- Step 5
- Step 6
- Step 7
- Step 8
- Step 9
- Step 10
- Step 11
- Step 12
- Step 13
+ Performance Analysis
+ Applets & WebStart
+ Maps & Imagery
+ X-Midas Interoperability
+ RMIF & Remoting
+ Installing NeXtMidas
+ Support & Maintenance
|
- Profiler Setup:
- Now go back to the shell console you will use to run NeXtMidas (this is the same one
you pasted the
-agentpath: line into.
- Start NeXtMidas using
nmprofile in place of nm
- The only difference between
nmprofile and nm is that
nmprofile tells the Java VM used by NeXtMidas to connect to the
NetBeans profiler.
- Once you run
nmprofile the Java VM will connect to the NetBeans profiler
allowing NetBeans to instrument the classes. This process will take up to thirty
seconds.
$ nmprofile
Starting NeXtMidas with profiler flags:
-agentpath:/opt/netbeans-5.5rc1/profiler1/lib/deployed/jdk15/
linux/libprofilerinterface.so=/opt/netbeans-5.5rc1/profiler1/lib,5140
Profiler Agent: Initializing...
Profiler Agent: Options: >/opt/netbeans-5.5rc1/profiler1/lib,5140<
Profiler Agent: Initialized succesfully
Profiler Agent: Waiting for connection on port 5140, timeout 1705
seconds (Protocol version: 2)
Profiler Agent: Established local connection with the tool
Profiler Agent: Redefining 100 classes at idx 0, out of total 418
Profiler Agent: Redefining 100 classes at idx 100, out of total 418
Profiler Agent: Redefining 100 classes at idx 200, out of total 418
Profiler Agent: Redefining 100 classes at idx 300, out of total 418
Profiler Agent: Redefining 18 classes at idx 400, out of total 418
nM>
- When you get to the
NM> prompt run the command you want to test.
To make it easier to identify the command it is best to run it in the background.
nM> demo/bg
|