Try it free

AQtime Pro Performance Profiling

Selective Profiling

Selective Profiling

With AQtime Pro, you are able to target and profile your whole application, or just specific regions. When you are a searching for a problem, profiling the entire application helps you find problematic regions. However, when you are working on a particular problem, having too many rows in the results may distract you from your goal.

AQtime Pro includes intuitive and easy-to-use features that give you the flexibility to profile an exact part of your application when you need to. That is, the features help you stay concentrated on your task and allow you to work more efficiently and faster:

The areas not only specify which segments of the application to be profiled, but also specify the profiling level: class, routine or line.

To help you in setting up a profiling session, AQtime Pro provides a detailed hierarchical list of all elements which are part of your project: assemblies, modules, namespaces, classes, routines and individual source files, all categorized for quick and easy retrieval:

Selective Memory Profiling

There are several predefined areas that help you specify the target code segments a lot faster:
  • Full Check - Using this area you can easily command AQtime Pro to profile all of the routines in all modules that are added to the AQtime project.
  • Profile Entire .NET Code - Enables profiling of all .NET modules and assemblies even if they are not included in any profiling area.
  • Profile Entire Java Code - Enables profiling of standard Java classes, even if the appropriate modules are not included into the AQtime project.
  • Profile Entire Script Code - Enables profiling of all routines executed by the Microsoft Script Engine. That is, you can profile scripts launched by TestComplete, a web browser or any other application that uses this engine.

Triggers and Actions let you enable or disable profiling during the application run. Profiling areas specify what you want to profile during the run, triggers and actions specify when you want to profile these. Actions also can be used to get profiling results at the desired application execution points or clear results at these points.

Triggers and actions