AQtime Pro is not just a single profiler — since there isn’t a single profiler that can give you a complete “picture” of your application. Instead, it is a series of cohesive profilers and panels working in unison to produce a clear snapshot of your application’s state at any moment in time. Here is a short list of benefits you’ll experience when you start using AQtime Pro.

• Time the execution of functions and lines and find the exact cause and nature of performance bottlenecks with AQtime’s Performance profiler. Besides timing, this profiler also tracks other crucial aspects of the application’s performance, giving you the power to --
  • Determine your code execution time in either user or user + kernel modes. This means that you can find the net execution time of your code, excluding time spent executing system-level functions and other threads as well as waiting for user input.
  • Check if your application causes an excessive number of memory page faults or CPU cache misses.
  • Determine how well the CPU can predict the execution flow of your code, and so on.
  Using the Performance profiler you can not only find a performance bottleneck, but also find out what caused that bottleneck.
   
• Find un-tested sections of source code at both routine and line levels with the Coverage or Light Coverage profilers. These profilers differ in the amount of data retrieved and in how fast they perform. With this feature you will no longer have to ask questions like “Did we really test and debug our applications thoroughly?”
   
• Trace and hunt down memory allocation and usage issues that are critical to the overall health and maintenance of your applications with the Allocation profiler. This profiler lets you easily see what objects exist in memory when results are generated. By comparing two result sets generated by the profiler, you can easily determine which objects were created or deleted between two result generations.
  You can use the Allocation profiler along with AQtime’s Monitor panel — a tool that gathers and displays information on memory and resource usage in real time.
   
• Use the Resource profiler to quickly discover what bitmaps, icons, BSTR strings and other resources are allocated by your application. By comparing two results you can easily find which resources were allocated or released between two result generations.
   
• Use the Reference Count profiler to monitor the creation and deletion of references to interface objects (for instance, references to COM objects). The profiler will pinpoint unreleased interface objects or those objects that were released earlier than expected.
   
• Visualize the caller-callee relationships of the application routines. Using the Call Graph and Call Tree panels you can easily see which routines call what routines in your application.
   
• Explore the binary code of your application using the Disassembler panel.
   
• Check possible links between classes and routines with the Static Analysis profiler. This profiler explores the debug information of your application and determines what routines include calls to other routines and what class methods call methods of other classes. The Static Analysis will also tell how many loop or conditional assembler instructions a routine’s binary code contains, what is the routine size in bytes and in source code lines, whether the routine uses MMX, SSE or SSE2 instructions.
  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, plus much more.
   
• The Sequence Diagram Link profiler, like Static Analysis, explores the debug information of your application, tracks links between routines (what calls what) and builds a UML-style diagram of functions calls in Microsoft Word or Microsoft Visio. This profiler is an excellent tool to know the links between routines without running an application.
   
• Track exceptions that occur during the application execution using the Exception Trace profiler.
   
• Measure the execution of stored procedures and SQL queries in databases with the BDE SQL profiler.
   
• Trace how your applications use dynamic link libraries using the Load Library Tracer profiler.
   
• Monitor the usage of API calls to produce code that works as expected across all Windows platforms via AQtime’s Platform Compliance profiler.
   
• Find unused source files in your Delphi and C++Builder applications with the Unused VCL Units profiler.