Labview application very runs poorly on better PC hardware

[ExarK]

What could cause a Labview application to run extremely poorly when deployed to a new higher performance PC verus the 4 year old one at my desk?  I'm using an Intel Core Due 2 on my desktop (2 cores), whereas my application is being deployed to an Intel Xeon (4 cores).  I've tried running both the old LV8.6 version of the software and the newer LV2011 version, and both are crawling to the point the application cannot be used.  The GUI isn't updating at the 4x per second, the mouse pointer is extremely jumpy when moved around the screen, and tabs/menus take several seconds to a couple minutes to be responded by the application.  On my desktop PC, the application runs smooth using the same executable file.  Both have the same OS (32-bit XP SP3) and both are running the same anti-virus software.

[LVbum42]

Are you accessing the deployed application remotely by any chance?

Regards,

Isaac S.

[ExarK]

No, everything is local to the computer I am running the deployed application on.

[thibber]

Hi ExarK,

If you launch Windows Task Manager while running the executable, do you notice a performance spike or a process that is comsuming a lot of resources?  Also, is it possible that your executable is looking for a file or library that might not be present on your new machine?

[ExarK]

Task manager shows that my application is consuming 25% overall CPU utilization, but under the performance tab it seems to use almost all (80-90%) of core 3, 25% of cores 2 and 4, and none of core 1. 

As far as external libraries, I'm not using any within my code except for DAQmx and the Labview RTE.  I have installed version 9.6.1 that we recently downloaded from NI.

[thibber]

ExarK,

- Can you supply additional information on what your application is doing?  

- Do you have the source code available with the LabVIEW Development Environment?  It sounds like LabVIEW is either hogging your resources (insert Wait functions into any loops you are running to periodically free up your processor) or that there is a memory leak (make sure you are closing your references correctly).

- Try building one of our shipping examples to run with your DAQ device (a simple analog input will do).  See if this runs slowly on the target PC as well.