Test Stand execution slows during long tests

[DanielJL]

I'm having an issue where the Test Stand execution of a sequence progressively slows down the longer my test executes.  The test suite I'm running is approximately 10 hours long and can have a call stack of between 3 and 8 sequences. I'm generating a HTML report and have On-The-Fly Reporting enabled.  The Trace feature is enabled.

[Norbert_B]

Did you set the option "Conserve Memory and show only latest results" (Report Option) as well as "Discard Results or Disable Results When Not Required by Model" (Model Option)?

Norbert

[DanielJL]

yes, the conserve memory is checked but the model option is not.  I need every step to be captured in the report.

[Perry_S]

Hi DanielJL,

What version of TestStand are you using? What operating system are you on? Does the memory bar on your task manager spike or steadily increase? Or is it constant? What about you CPU usage, is it spiking or constant? What happens when you don't do on the fly reporting?

Perry S.

[DanielJL]

Hi Perry,

Test Stand version 4.2.1

Windows XP SP3

The memory steadily increases as the test continues.  The CPU is relatively consistent once the sequence is loaded and execution has begun.

We ran into the issue where test reports are not generated if TestStand crashes during an execution.  Therefore, we must use on the fly reporting to ensure that the Test Report exists up to the point of the software crashing.

Thanks,

Daniel

[~jiggawax~]

How many steps are set to report?  One thing you need to realize is that every step that executes that is set to record places information in Locals.ResultList.  If you run for ten hours and are recording a step every second (or even every minute) then that could get VERY large.

[Norbert_B]

---

@DanielJL wrote:

yes, the conserve memory is checked but the model option is not.  I need every step to be captured in the report.

---

You have to enable this option as well, otherwise, increasing memory consumption over time is "works as expected". Using On The Fly Reporting will create the report in parallel to the execution, so discarding the entries in the result list must not have any effect on the report. If it does, it is something which has to be analyzed by TestStand R&D (so please contact your local NI branch then).

Norbert