How does profiling via root methods work?
The code subset to profile can automatically be identified based on whichever profiling root method you provide. The given method is instrumented and all methods that it calls transitively (a call subgraph) are discovered and instrumented automatically while the target application runs. You can select multiple roots and thereby instrument multiple subgraphs.
You can use any method as a root (for example, a method which has previously been identified as a general bottleneck) to see which of its callees contribute most to the execution time. Alternatively, the root method can be the entry point into the part of the Java code that you are currently interested in (for example, the doGet() method of your servlet). In both cases, only the code of this method and its callees are instrumented.
If any of these methods are called in a thread that hasn't previously called the given root method, the instrumentation injected into these methods does nothing and returns immediately, although it cannot be disabled completely.
Applies to: NetBeans 5.5/6.*/7.*
Back to NetBeans IDE Profiling FAQs
Back to NetBeans User FAQs