TS_EngineNewExecution () takes about 10 seconds on one machine, 1 on another

[bmihura]

How can I stop the 10 second delay? I've rebooted, and the function isn't failing, it's just too slow.

[bmihura]

Also... the 10 second delay only happens whenever I'm running in debug mode on either computer. It doesn't have to do with the particular computer.

[Scott_Richardson]

To bmihura -
Questions:
1) What version of TestStand are you using?
2) Are you developing an Operator Interface? What development language?
3) Are you calling New Execution from the OI or from a step using the ActiveX Adapter?
4) What do you mean by "debug mode", are you debugging the TestStand process with a ADE, which one?

Scott Richardson (NI)

[bmihura]

Answers:
1) 2.0.1f1
2) LabWindows/CVI 6.0.0
3) From the OI
4) I�m debugging it with LabWindows/CVI 6.0.0, assuming ADE means "applications development environment"

[Scott_Richardson]

To bmihura -
You state that you see the delay when you are debugging the OI using CVI. I assume that do not see as long of a delay when you run the debuggable OI exe without attaching to the CVI ADE. If correct, what is the estimate of time it takes when not debugging?

If you are getting a lot of debug output, I know that this can slow down a debugger. Are you seeing a lot of debug output?

What speed is your CPU and how much memory do you have on the these systems?

Scott Richardson (NI)

[bmihura]

When not debugging, the delay is under one second.

I'm not getting any debug output, although I'm not sure what "debug output" means. I consider "debugging" to be CVI's ability to stop at breakpoints then step through the code and see variables' values.

The CPU is 2.4 GHz, memory is 512M.

[Scott_Richardson]

To bmihura -
I am thinking of the traditional "Debug Output" that is available in MSVC and CVI 7.x, i.e. calls to the SDK function OutputDebugString the debugger collects. I do not think that CVI 6.0 supports this. These messages can slow down a debugged process.

I ran the default CVI OI from TS 2.0.1 in the debugger on my system, which is similar to yours, and the performance was almost identical, under a second.

Questions:
1) Do you see this performance hit when debugging your OI when you run a client sequence that is empty and without using a process model, i.e. Run MainSequence?

2) Do you see this performance hit when debugging your OI when you run a client sequence that is empty but using your pro
cess model?

3) Do you see this performance hit when using the default CVI OI that ships with TestStand?

Scott Richardson (NI)