Multi-Threading Best Practice

[Jeremy.JPG]

I have very little experience with multi-threading. I completely understand the concept, but I have never had a situation until now where I could use it. I have a subsequence that I'd like to run in its own thread just to save some time (even though I don't think it'll take more than a millisecond to run). In the subsequence's Execution Options, I have it set to Use New Thread. Is that the proper way to do it? Do I need to do "garbage collection" with the threads and close them manually? What are some best practices for multi-threading in TestStand?

Thanks,

Jeremy

[santo_13 · Accepted solution]

Multi-threading has overheads. If your task is not significant enough, your execution will be slower when multi-threading.

Yes, set the run in a new thread in the sequence call step. AFAIK, you don't need to do garbage collection as long as other tasks are not dependent on the one running in a new thread.

[Jeremy.JPG]

Thank you. You saved me a lot of time searching and scouring forums. I feel like it can be tough finding some TestStand information out there. Especially when it comes to syntax.