"Another Steve" wrote in message
news:506500000008000000044A0000-1021771306000@exchange.ni.com...
> Win2000
>
> I have an application that runs using at most 10% CPU time when run
> either under Labview or as an .exe on a computer with Labview 6.0.2
> installed. However, on separate (but similar spec) computers with the
> run time engine installed (using the installation generated by the
> same build that compiled the application) the application takes 100%
> cpu and only runs at about 1/10th the speed. As a general issue I
> would be interested to know if an application is expected to run
> differently under the run time engine. It raises significant
> development issues if it does.
>
> More specifically, I can isolate the code that is running
> s
ubstantially slower under the RTE to a loop writing to the value
> method of a property nodes (I have reasons for not using
> locals/terminals, and it works fine in the development environment). I
> can't however recreate the problem with a simplified simulation of the
> same type of code, so it is beyond my resources to track the problem
> down. Is there anything simple I could try? Is the latest RTE
> available for download?
>
> My only thought is I went through a stage of getting a few 'insane
> object' errors, which seemed to resolve themselves. However, if I copy
> and paste the entire BD to a new vi they reoccur, and I cant save the
> new version.
>
> Any suggestions, short of re-wiring my code from scratch on the
> offchance it is a one-off problem?
Whenever you have a loop that has a possibility of running in close to zero
time put a "wait until next ms multiple" function in it with an input value
of 100. That will prevent the loop from hogging cpu time. This is probably
not
it, but I thought I'd throw it out there.