You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
labview source/gRPC lv Support/Server API/Server/Get Server DLL Path.vi
This VI is used in many places throughout the code to return the path to the server DLL. The code is structured so that the correct DLL path is determined on first call and then simply passed out (via a feedback node) on subsequent calls. However, because this VI is set with pre-allocated clone reentrancy, and most other VIs that call it are also set as pre-allocated clones, this VI is cloned all over, which results in the VI always running "first time" and not using the built-in feature to only determine the path once.
This becomes especially apparent when these VIs are built into a PPL. During runtime, I have found that the VI to determine the PPL path (NI_PackedLibraryUtility.lvlib:Packed Library Path.vi) takes ~1-2 seconds to run. Due to the reentrancy settings of the VI, this causes this VI to run many times during gRPC initialization and cleanup, proportional to the number of gRPC services configured.
I have tested setting this VI as a non-reentrant VI and it drastically improves runtime execution in a PPL for my application.
AB#2536610
The text was updated successfully, but these errors were encountered:
labview source/gRPC lv Support/Server API/Server/Get Server DLL Path.vi
This VI is used in many places throughout the code to return the path to the server DLL. The code is structured so that the correct DLL path is determined on first call and then simply passed out (via a feedback node) on subsequent calls. However, because this VI is set with pre-allocated clone reentrancy, and most other VIs that call it are also set as pre-allocated clones, this VI is cloned all over, which results in the VI always running "first time" and not using the built-in feature to only determine the path once.
This becomes especially apparent when these VIs are built into a PPL. During runtime, I have found that the VI to determine the PPL path (NI_PackedLibraryUtility.lvlib:Packed Library Path.vi) takes ~1-2 seconds to run. Due to the reentrancy settings of the VI, this causes this VI to run many times during gRPC initialization and cleanup, proportional to the number of gRPC services configured.
I have tested setting this VI as a non-reentrant VI and it drastically improves runtime execution in a PPL for my application.
AB#2536610
The text was updated successfully, but these errors were encountered: