Teststand response time

[Thomas_Richter]

Hello everybody,

i'm using Teststand 2010 since short time and used 3.5 before. I'm experiencing incredibly slow response from Teststand while editing. Regardless of the action: inserting a new step, clicking anywhere, even when editing an expression, Teststand makes breaks of up to 5s length. I've the impression to work on a 386 machine. Just a click and the program stops responding for several seconds.

I've also installed it on a test machine, where the sequences are on the local harddisc. That one responses better, but also jerkily. It's really annoying. I'm not talking about the performance at run-time, that one seems to be OK.

Actually, we stuck with TS 3.5 because 4.0 was already that slow.

I'm working on a dual core with 4GB RAM. CPU load stays low.

Any comments?

Thomas

[Rodéric]

tracing enabled?

[dug9000]

Is anything running in the background while you are editing? An execution in TestStand or another application perhaps? Does this happen on a clean install with example sequence files or is something specific to your system required before you see this problem happening? There must be something unusual about your machines or the software running on them, since this does not typically happen.

-Doug

[dug9000]

One idea I just thought of is search directories. If you have customized your search directories and added network paths to them, that could be the source of the problem. If so you might try removing any custom search directories you've added and see if the problem goes away. Just a guess though since I have no idea what is different about your machines. You might try removing and then slowly readding your customizations (if any) to see when the problem starts to occur and thus determine the cause.

Hope this helps,

-Doug

[Captain_Jack]

We've seen this type of behavior when using source control (ClearCase) in a dynamic view. We think that this was because the TestStand editor constantly accesses the file in disk for every action combined with the overhead of ClearCase, would result in an extremely unresponsive editor.

Search paths with the search subdirectories turned on could be causing this behavior as well. Try setting the search paths to only those TestStand and your sequences absolutely need.

-Jack

[Thomas_Richter]

Hello,

thanks for your answers so far. Unfortunally none of your suggestions apply. I found out what's the problem (at least i think so ;-): TS seems to reload files each time it evaluates the parameters or expressions. If the file is on the local hard disc, it works. But if the file is on the network, it gets slow. You can watch on the task manager, each time you edit an expression, TS writes and read quite a lot on the network.

@NI: Does it have to be that way? I usually work on the network..

Best regards,

Thomas