Results failing to collate
Question ID: 107608

In our Performance Center 12.50, we had a test run stated it collated properly. However, the .eve and .map files from the test was missing from the Raw Results folder. This test was run with 1000 Vusers using two scripts created with the Web HTTP/HTML protocol for a test run of 8 hours with a fifteen minute ramp up and fifteen minute ramp down.
Both scripts had Extended logging enabled with Parameter substitution and Data returned by server enabled. However, they had it set to "Send messages only when an error occurs" was set to 100 KB cache log size.

From the Controller Output messages there was over 8704 errors in this test. We used four Load Generators for this test.

Marked as spam
Posted by (Questions: 144, Answers: 1)
Asked on April 26, 2017 5:14 pm
Answers (1)
Private answer

To run a 8 hour and 30 minute test, logging should be fully disabled for these kind of test. According to HPE best practices ''you should disable all logging by ensuring that the Enable logging checkbox in the runtime settings dialog's Log branch is unchecked, unless you need it for debugging purposes (and with no more than 10 Vusers).

Running many Vusers with logging can affect the test results because logging is a time-consuming activity. Each log message also takes up space on the disk, and in extreme circumstances, particularly on long tests, could cause the disk to fill up. You should also disable the Send messages only when an error occurs option, since there may be a lot more errors than expected.''

For the Controller Output messages of 8704 errors in this test. I highly suggest that the two scripts be reviewed and the errors fixed that was received during the test.

You will need to drill down on the % Disk Time for each LG, I positive it will show that maxed out physical disk on the LGs at various points within the test.

When the physical disk runs out of space at points during the test, these file are not create, thus they are going to be missing from the results.

Run a one hour test to ensure that the scripts are functioning as needed before running a 8 hour test. When running a long test, logging should be fully disabled.

Marked as spam
Posted by (Questions: 0, Answers: 152)
Answered on April 26, 2017 5:15 pm

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top