06-04-2020 02:19 PM
'Dynamic To Waveform Array.VI' is a sub VI that is found in a few signal filtering VI's in LabVIEW.
This VI seems to be taking up an absurd amount of run time on my Real Time system.
It took 61210.5 mS of active run time, and I only ran the anaylizer for a few minutes.
This is the longest running VI in my list, and It is one of the most called VI's
When you look at this VI it is a very simple feed through of data with a red dot
auto coercion,
I'm using the smoothing filter express VI in several places in the code, and this vi seems to be used a few times within the express VI.
Why is this sub VI so time expensive?
I fixed the issue by replacing the express VI with a custom built VI that does almost the same thing at a 100th of the time cost.
I included my original resource report.
So, NI what is the story for this?
Any why is it not cloned or inlined? I would think the cost of code space would be a fair trade for performance increase.
06-04-2020 03:00 PM
Can you post the code and a few of the vi's that surround this vi. My guess is that this is only part of the problem. You should not be using Dynamic data in the first place. If you post your code we will help you get rid of the dynamic data issues.
06-04-2020 03:22 PM - edited 06-04-2020 03:23 PM
This is a VI that ships with LabVIEW. If you convert the express VI to a standard VI you can drill down and find the dynamic to waveform array.
It really isn't a choice to use dynamic data. It's part of the VI that comes from NI.