Previous Next        Current Page: NeXtMidas Training / NetBeans - Part 3 (Profiler) / Performance Analysis / Step 4
back
+ 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)   
+ NetBeans - Part 1 (Setup)   
+ NetBeans - Part 2 (GUIs)   
- NetBeans - Part 3 (Profiler)   
   + About Profilers   
   + Profiler Setup   
   - Performance Analysis   
      - Step 1   
      - Step 2   
      - Step 3   
      - Step 4   
      - Step 5   
+ Eclipse - Part 1 (Setup)   
+ Eclipse - Part 2 (GUIs)   
+ Primitives   
+ WebStart   
+ Maps & Imagery   
+ X-Midas Interoperability   
+ RMIF & Remoting   
+ Installing NeXtMidas   
+ Support & Maintenance   
+ File Handlers   
  • Performance Analysis:
    • Often times the best approach is to expand the "biggest red bar" on each level until you find the methods that are driving the performance of the application.
      Click image for larger view.
    • In this example the calls to Math.log(double), Math.abs(float), and Math.max(double,double) in Logarithm.SS(..) are driving the performance of the FFT command.
      • Before you go off thinking that those methods are "slow" look in the "Invocations" column and note that they are being called millions of times...
    • Once you have identified the "slow" part of your primitive it is now time to ask yourself, "How can I make it faster?"
back