There are two possible things you can do.
1) Lower the thread priority of teststand execution threads. You can do this using the Thread Priority synchronization step type available in TestStand 2.0 and greater. NOTE: If you are not using the CPU for anything else it might still show CPU usage of 100%, but as soon as something that is higher priority needs CPU time it will give less time to the teststand threads.
2) Have your teststand threads sleep periodically. You can do this using the Wait synchronization step type. If you wait for a few milliseconds every so often in your sequences, they will give up CPU time during the time that they are waiting.
One thing to keep in mind is that getting CPU usage below 100% for a process is only useful if you have something e
lse for the cpu to do. In otherwords, one generally wants to keep total CPU usage as close to 100% as possible to make things as fast as possible. For maximum performance I recommend the first solution of lowering the thread priority if you find that other processes running on your computer are becoming unresponsive.
Hope this helps,
Doug
NI
