In Vugen, the transaction time includes the ''wasted time'' but it is subtracted from transaction time when displayed in Controller and Analysis.

Explanation of ''wasted time''

The concept of ''wasted time'' was introduced in order to distinguish between actual time spent on processing and displaying information, from Human/idle-waiting overhead. Wasted time is calculated as a factor of unnecessary waiting, as illustrated in the following examples:

1. Rendezvous are added to wasted time, since the client Vuser could theoretically continue executing, but has opted to wait for other Vusers to meet at certain points of execution.

2. Any silent waits (i.e., via TE_wait_silent), where the context or text has already been displayed, but the Vuser still waits to ascertain that it is stable. (Functions such as TE_wait_text() have lr_wait_silent embedded in it.) This is to ensure that the text is actually stable before continuing. It is considered wasted time, since the Vuser really did not have to wait, but did just to make sure the text appeared and stabilized.

3. Any User Input time is considered wasted time, since the application is not engaged in processing or displaying information. Even if the typing style is modified (i.e., via TE_typing_style), the total duration of the typing is considered ''wasted time.''

4. Explicit sleep statements are not considered ''wasted time'' since it may be argued either way. If you want idle waits to be included in ''wasted time,'' use TE_wait_silent().

5. For Winsock script, time to compare the difference between the receiving buffer and data in the data.ws is counted as wasted time.

6. For Web script, the time taken for web_reg_find or web_reg_save_param functions to look for a particular string in the response buffers, is counted as wasted time.