Profiler Features:
In this chapter, we supply a brief presentation of the key features of our Profiler.
Monitoring Methods
Our Profiler can map the key performance-sensitive .NET methods to TMTP transactions, and users can view and analyze the transactions topology diagrams in TMTP to find out the bottle-neck methods which cause performance problems. The way by which the Profiler supply this key feature is: while the profiler is initialized by CLR, the Profiler need read the configuration file to get the methods list need to be profiled, in the case of these methods was invoked by CLR, Profiler will interpose arm-instrumented code to the profiling points.
Retrieving and modifying Contexts
Retrieve function context values in runtime stack, and set these values to TMTP Transaction property context values. In most of cases, we retrieve string type(.NET type "System.String") fields of function arguments.
Multiple-Thread Supports
The .net methods being profiled can be invoked simultaneously by a dozen of threads running in CLR process.
Matching with Class or Interface
We can monitor .net method by the name of class or interface. If we use interface methods to be profiled , all methods of the classes implemented that given interface is supposed to be candidates of Profiling points to our Profiler.