Open VI reference is very slow if VI is not already loaded in memory

[TheQ]

If you open the VIs often, look into how the Actor Framework calls VIs asynchronously.  In the "Launch Actor Core.vi"  it does it in a loop because the opening of the reference take a lot of time but you can use the same reference to spawn multiple clones.  Not sure how this works with VIT rather then VI though.

[zigbee1]

Thanks TheQ for recommending using Actor Framework, I will definitely consider it for new projects. It appears that the problem is gone after I do a "mass recompile". Truth be told, this project I got from someone who was running LV2013 even though he converted it to LV2015 long ago. So I suspect one of the child VI was still LV2013 and it took too long to convert it to LV2015. Thanks RavensFan for bring it up !