Performance Considerations (Mobile Module)
LabVIEW optimizes Mobile VIs for data size, speed, and code size, in that order.
Mobile devices run on battery power. A user typically runs Mobile applications for short intervals and then expects the device to switch to low power mode until the next time he or she needs it.
To conserve battery resources, include a Wait For Front Panel Activity function or an Event structure in a Mobile VI to create a wait state to save battery power. Adding a wait state allows the Mobile VI to go to sleep if you do not tap the screen for the duration you specify in the preference settings on the Mobile device.
Mobile VIs use cooperative multitasking. Therefore, you can design Mobile VIs to have parallel loops on the block diagram. One loop runs for a time slice of approximately 50 ms, and then another loop runs for a time slice. Mobile VIs automatically use cooperative multitasking when you use two or more nodes that a wire does not connect. However, Mobile VIs with parallel loops run slower than VIs with serial loops.
If you set the execution priority of a Mobile VI to subroutine, LabVIEW serializes execution of the VI. The Mobile VI runs faster, but the user interface does not get any CPU time, and the application might become unresponsive. Place a Wait Until Next ms Multiple function on the block diagram to accommodate this limitation.
Using subVIs can affect parallel execution, which affects performance.