上面图中的Form1那块那些列 什么routione Name time time with children hitcount 都是什么意思？ 简单的一个流程应该是怎样的？
上面图中的Form1那块那些列 什么routione Name time time with children hitcount 都是什么意思？ 简单的一个流程应该是怎样的？
终于把图贴出来了 The Allocation profiler traces the memory usage within your applications during the profiler run. It reports how many objects of each class exist, how many memory blocks are allocated, how much memory is occupied by objects and blocks, etc. The profiler gathers a lot of information: it traces call stacks for objects and memory blocks, determines references between different managed objects, etc. Using the Allocation profiler you can easily find memory leaks in your unmanaged (i.e. non-.NET) applications. Although the common language runtime (CLR) reclaims all the memory allocated for the objects of a managed application when the application run is over, this profiler can still be used with such applications. You can employ it to trace objects during the application run. Using the Monitor panel when running the Allocation profiler, you can view the allocation information in charts or histograms, which helps you trace the memory usage in real time. The Resource profiler follows how your application exploits Windows resources (fonts, brushes, bitmaps, and other graphic components, registry, COM objects, print spooler and so on) during the profiler run. It reports what these resources are, how many resources of each type were created up to given moment, how many of them still exist, how much memory is occupied by the resources in use, what errors in resource management functions occurred during the run, etc. The profiler can help you find resource leaks (unreleased resources) and resource errors in managed and unmanaged applications. For each occupied resource instance, the profiler keeps its call stack of functions calls, which lets you easily discover how this resource instance was allocated. The Coverage profiler determines whether the function or line was executed during the application run. It also counts the number of times a routine (or line) was executed during the profiler run. Using this profiler you can easily find what application areas your tests "cover" and what was left untested. The Static Analysis profiler will tell you which methods exist in the application, where they are called from in the source code and what they call in turn. This does not tell you if and when the calls will execute, but it does give a full report of method inter-dependence in the source. See it as an intelligent overview browser of the debug information that is linked into the executable. A powerful addition to the Static Analysis profiler is the PE Reader panel. It also performs the analysis of your application statically and provides detailed information about modules used by the application. For example, it shows tables of imported and exported routines, module base addresses, entry points of routines and their offsets in the import address table, etc.The Sequence Diagram Link profiler builds a UML-style diagram of function calls in the profiled application and displays this diagram in Microsoft Word or Microsoft Visio. The Platform Compliance profiler reports what Windows versions support the API calls in the source. The Exception Trace profiler monitors the application execution and, if an exception occurs, displays the exception call stack in the Event View panel. Since Exception Trace does not slow down the application execution, it can be very convenient to use if your main goal is tracking down an application exception. The Function Trace profiler traces the routine calls during the profiler run and logs call stacks for each call. Native-code and managed application profiling is supported (including 64-bit code support). It provides you with comprehensive information on how any routine is invoked, which parameter values are passed to it and some other routine characteristics. This profiler provides an opportunity to process actual call stack data in real-time. Source code modifications are not needed - Function Trace automatically performs actions, that otherwise, could only be done by introducing hundreds of trace-message lines in the source code. The Load Library Tracer profiler traces the loading and unloading of dynamic link libraries during the application execution. Using the profiler you can detect which libraries are loaded and unloaded too often (and thus impact the overall application performance) and optimize the use of them.
我常用：上面图中的Form1那块那些列 什么routione Name time time with children hitcount 都是什么意思？ 简单的一个流程应该是怎样的？非常容易的 Routine Name就是函数名； Time是这个函数自身花费的时间； Time with children是这个函数自身加上这个函数内部调用的其他函数花费的总共的时间； Hit Count是这个函数的执行次数；你是不是英文不太懂啊。AQTime 是用来做Profiling 剖析的； 就是如果你觉得程序慢，或者有内存泄漏方面的问题， 就可以用AQTime来剖析一下，看看时间都花在哪些函数上，内存都是被哪些对象占用的。经验之谈，加入到Profiling中的函数要尽量的少，当Hit Count超过 一千万时 会有比较大的误差，（几秒）。需要更多帮助，请到我博客上留言，或者发邮件给我吧 [email protected]
简单的一个流程应该是怎样的？
简单的一个流程应该是怎样的？
The Allocation profiler traces the memory usage within your applications during the profiler run. It reports how many objects of each class exist, how many memory blocks are allocated, how much memory is occupied by objects and blocks, etc. The profiler gathers a lot of information: it traces call stacks for objects and memory blocks, determines references between different managed objects, etc. Using the Allocation profiler you can easily find memory leaks in your unmanaged (i.e. non-.NET) applications. Although the common language runtime (CLR) reclaims all the memory allocated for the objects of a managed application when the application run is over, this profiler can still be used with such applications. You can employ it to trace objects during the application run. Using the Monitor panel when running the Allocation profiler, you can view the allocation information in charts or histograms, which helps you trace the memory usage in real time.
The Resource profiler follows how your application exploits Windows resources (fonts, brushes, bitmaps, and other graphic components, registry, COM objects, print spooler and so on) during the profiler run. It reports what these resources are, how many resources of each type were created up to given moment, how many of them still exist, how much memory is occupied by the resources in use, what errors in resource management functions occurred during the run, etc. The profiler can help you find resource leaks (unreleased resources) and resource errors in managed and unmanaged applications. For each occupied resource instance, the profiler keeps its call stack of functions calls, which lets you easily discover how this resource instance was allocated.
The Coverage profiler determines whether the function or line was executed during the application run. It also counts the number of times a routine (or line) was executed during the profiler run. Using this profiler you can easily find what application areas your tests "cover" and what was left untested.
The Static Analysis profiler will tell you which methods exist in the application, where they are called from in the source code and what they call in turn. This does not tell you if and when the calls will execute, but it does give a full report of method inter-dependence in the source. See it as an intelligent overview browser of the debug information that is linked into the executable.
A powerful addition to the Static Analysis profiler is the PE Reader panel. It also performs the analysis of your application statically and provides detailed information about modules used by the application. For example, it shows tables of imported and exported routines, module base addresses, entry points of routines and their offsets in the import address table, etc.The Sequence Diagram Link profiler builds a UML-style diagram of function calls in the profiled application and displays this diagram in Microsoft Word or Microsoft Visio.
The Platform Compliance profiler reports what Windows versions support the API calls in the source.
The Exception Trace profiler monitors the application execution and, if an exception occurs, displays the exception call stack in the Event View panel. Since Exception Trace does not slow down the application execution, it can be very convenient to use if your main goal is tracking down an application exception.
The Function Trace profiler traces the routine calls during the profiler run and logs call stacks for each call. Native-code and managed application profiling is supported (including 64-bit code support). It provides you with comprehensive information on how any routine is invoked, which parameter values are passed to it and some other routine characteristics. This profiler provides an opportunity to process actual call stack data in real-time. Source code modifications are not needed - Function Trace automatically performs actions, that otherwise, could only be done by introducing hundreds of trace-message lines in the source code.
The Load Library Tracer profiler traces the loading and unloading of dynamic link libraries during the application execution. Using the profiler you can detect which libraries are loaded and unloaded too often (and thus impact the overall application performance) and optimize the use of them.
简单的一个流程应该是怎样的？非常容易的 Routine Name就是函数名； Time是这个函数自身花费的时间； Time with children是这个函数自身加上这个函数内部调用的其他函数花费的总共的时间； Hit Count是这个函数的执行次数；你是不是英文不太懂啊。AQTime 是用来做Profiling 剖析的； 就是如果你觉得程序慢，或者有内存泄漏方面的问题， 就可以用AQTime来剖析一下，看看时间都花在哪些函数上，内存都是被哪些对象占用的。经验之谈，加入到Profiling中的函数要尽量的少，当Hit Count超过 一千万时 会有比较大的误差，（几秒）。需要更多帮助，请到我博客上留言，或者发邮件给我吧 [email protected]