Previous Next        Current Page: NeXtMidas Training / NetBeans - Part 3 (Profiler) / About Profilers / What do we look for?
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   
      - Why use a Profiler?   
      - What do we look for?   
      - WARNING!!!   
   + Profiler Setup   
   + Performance Analysis   
Eclipse - Part 1 (Setup)   
Eclipse - Part 2 (GUIs)   
Primitives   
WebStart   
Maps & Imagery   
X-Midas Interoperability   
RMIF & Remoting   
Installing NeXtMidas   
Support & Maintenance   
File Handlers   


  • What do we look for?
    • Profilers are used to identify "problem" areas, such as:
      Memory Leaks (Not Possible in Java)
      Memory leaks are those where memory is no longer usable and can not be freed up for reuse. Memory leaks are not possible in Java because the Java Garbage Collector cleans up any unused memory.
      Useless Memory
      In Java a "memory leak" is said to occur when memory is being used that is no longer useful. This differs from a true memory leak because the memory is still (theoretically) usable -- hence why the Java Garbage Collector does not clean it up.
      Performance "Hot Spots"
      A method (or set of methods) whose cumulative performance drives the execution time of the program.
      In NeXtMidas these usually are found inside the process() method of a DSP primitive.

back