First, let's clear a misconception. Mass-compiling is actually a mass conversion of an entire VI herarchy of old VIs to the current labVIEW version. It has no influence on speed if all your VIs are already saved in the current LabVIEW version. (Only a freshly converted VI from an old LabVIEW version is a bit slow until saved, so make sure that all subVIs are current)
A faster PC will help
IF your problem is truly CPU limited. This is difficult to tell without looking at the code.
What else does your LabVIEW program do (e.g. processing and displaying the image at a high rate)? Is it possible that your code does a lot of unecessary work? How many parallel loops are there?
Are all front panels of SubVIs closed while runing unless they really need to be visible?
What else is running on the PC? Could it be frames are missed if other stuff happens (antivirus, windows updates, etc.). Are there any other USB devices on the same controller (e.g. USB mouse, etc.)?
Have you played with priorities? A typical VI will also speed up a bit if you disable debugging.
If you don't mind, post a simple version of your code. Is it clean and streamlined or cluttered with local varables and property nodes? Are heavy calculations only done when needed or with each loop iteration?
Message Edited by altenbach on 05-08-2005 02:25 PM