LabView Dashboard

[Danny Diaz]

Originally Posted by kaszeta

Any ideas on speeding this up?

I've made some performance improvements in the update I provided here, give it a shot if you haven't already. Turns out that in LabVIEW 8.0 if you have any "while" loops that could go on forever in your code that LabVIEW thread can potentially run out of control and can send processor utilization through the roof (i.e. there are no "blocking" calls that forces the loop to wait for "something to happen"). I noticed this on team 418's laptop that it was dreadfully slow because the while loops were eating so much of the processor - oddly enough I didn't have this problem on a comperable desktop, but then again you never see any problems when you're developing software just when it gets out into the public . I added "wait for millisecond multiple" VI's in each loop which caused the thread to block (or yield to other processes/threads) and this greatly enhanced performance on the machine (and thusly I submitted the update). I debated on whether or not to have the packet processing delay automatically start at 10 by having a "10 + packetprocessingdelay" in the code but that would honestly be arbitrary and might or might not be right on a given machine. Sure, the 100ms multiple I added was also arbitrary, but sometimes you have to just make a decision and live with it.

Let me know if the update helps. I can gain access to a Mac OS X 10.4.4 desktop here at NI for a bit (through the careful use of bribery) so if this doesn't seem to do the trick I can potentially see what else might need a little TLC.

-Danny

[kaszeta]

Originally Posted by Danny Diaz

I've made some performance improvements in the update I provided here, give it a shot if you haven't already.

That's the version we're using.

Originally Posted by Danny Diaz

Turns out that in LabVIEW 8.0 if you have any "while" loops that could go on forever in your code that LabVIEW thread can potentially run out of control and can send processor utilization through the roof (i.e. there are no "blocking" calls that forces the loop to wait for "something to happen").

I'll check the Activity Monitor tonight when I run it to see what's going on. I'll also probe around and see if I can find anything else that's going on, although my labview skills aren't what they used to be...