Hi Senthil,
I recollect one similar code with wire branching. They have provided explanation about how compiler makes decision about which branch getting executed first based on memory management. It is available in LabVIEW Help document under memory management.
The example code contains
1) Numeric Array – an Incoming Array (of size 1000) of numbers (double data type = 8 bytes).
2) two nodes directly connected to the Numeric Array
a) Index node to pick a single element from the array.
b) Replace an element in the incoming array.
Ideally, the branching of wire will copy, so it should allocate an additional 8k of memory. But the LabVIEW compiler will optimize the memory allocation by fixing the order of execution among the branches of wire.
If both branch has nodes like delete array or replace array, LabVIEW will be forced to duplicate the incoming array as it cannot reuse memory by fixing the order of execution. In that case, the order of execution can be any order.
I think it is a similar way the complier decides the order of execution when there is a subVI that you showed during the event.
Please find the link about how LabVIEW performs bottom up (subvis to top level vis) for these optimizations.
https://forums.ni.com/t5/LabVIEW-Development-Best/LabVIEW-Performance-and-Memory-Management/ta-p/351...
