Main operation modes:

Figure 1 illustrates the basic components of PMON. These are described in detail below.

 

Figure 1

 

User interface

 

In this mode, referred to hereafter as "Pmon Utility", you operate the utility interactively while running the application you want to test. Refer to Figure 2 for the features described below.

 

 

 

Figure 2

 

First, select the events you want to measure through the two drop-down list boxes, and then start the counters by pushing the "Start" button. The "Start" button will now display "Stop." You will see the counters updated every second. When you hit the "Stop" button, the summary of this measurement will be displayed in the notification window. You can then copy these messages to the Windows* clipboard or to a file.

 

There are several options for starting/stopping the counters, and for logging the results into a file. For details, see the explanations later in this guide. Also, the source code of this utility is supplied with this package and may be used for reference or modified as needed.

 

Command line interface

In this mode you activate the PMON utility along with some command line parameters. The command line parameters allow you to activate the utility, select the events, start and stop the counters, and log the results to a file. Command line implementation can be done by running it from a Windows 95 DOS* box, by creating and editing the properties of the utility’s desktop icon or by using a test tool utility such as Microsoft* Visual Test.

Note: Each time you call this utility it loads again and executes.

 

Programming interface

In this mode, referred to hereafter as "Pmon API", you interface with the DLL APIs from your code or test tool utility. Loading, initializing the DLL, starting/stopping and retrieving the information is done by the user from the application code. This is most accurate and non-intrusive mode, however it requires some programming and you must have the source code of the application under test. This mode can also be used with a test tool utility.

Table of Contents
Chapter 5