NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TS execution rate slows down over time?

I have noticed this issue in the past, but with V3.0, after numerous continous hrs of operation, the execution rate slows to a crawl. Its not disk space related as I have 4G free. I have a Win2000 box with 512M RAM, albeit a 450Mhz PC.
0 Kudos
Message 1 of 4
(3,206 Views)
Based upon the information you provided, this sounds more like a memory issue. If the reporting is not set to "On The Fly", then all of the reporting information is stored in memory and not written to disk until the test completes. With TS 3.0, this option is available under the reports section.

Hope this helps

Mike
0 Kudos
Message 2 of 4
(3,206 Views)
To RJM -
Use the task manager application to monitor the memory usage of the application that is using TestStand. Use the View>>Select Columns dialog box to define what to display. The best columns to look at are:
Mem Usage (what is currently being used)
VM Size (all that can be used)
Handles
Threads
USER Objects
GDI Objects

Scott Richardson (NI)
Scott Richardson
https://testeract.com
0 Kudos
Message 3 of 4
(3,206 Views)
RJM -
I assumed that you know this but TestStand does collect results as it goes so if you are running for a long time, the set of results will turn out to be quite large and will consume a lot of memory.

You could verify that the collection of result is your concern if you enable the Disable Results Recording option on the Execution tab of the Station Options dialog box.

The previous suggestion to use the TestStand 3.0 with its on-the-fly report generation or database logging features along with enabling the conserve memory options on the Model Options dialog box is one way to prevent the default TestStand process model from collecting results after they have been processed by the model.

Scott Richardson (NI)
Scott Richardson
https://testeract.com
0 Kudos
Message 4 of 4
(3,206 Views)