Respected Contributor.
Respected Contributor.

Viewing pacing problems in Analysis


I'm using PC and Analysis 12.61.

I noticed that if we have large numbers of warnings like these:

Warning: Iteration pacing cannot be reached (pace time = 1.00, actual time = 1.26). [MsgId: MWAR-15995]

Then we sometimes can't reach our target HPS.  The problem is that it's not obvious whether the failure to reach the target is an issue with the scenario itself or the app under test without looking at the vuser logs.

It would be great if there was something in the results that showed us a count of these warnings.  Does such a thing exist?  I don't see it in Analysis.




The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.