10-07-2019 01:12 PM
Yes, my mistake.
I retested:
After 1st run with a constant of 10000, the task manager showed about 774MB (up from 60MB).
I then changed the constant to 20,000 and ran again. The Labview memory in Task manager jumped to 1774MB (i.e more than doubled).
*The Output array size in this case was 175MB.
I pressed run again (still 20000) and got 1910MB in Task manager.
Running again and again with the same (20,000) parameter gave the same 1910MB result (stabilized).
So there's seems to be a lot of allocation going on.
The question remains if there's a better way of implementation in order to avoid this huge allocations.
10-07-2019 01:18 PM
You originally attached two quite different VIs. Which one are you running "again and again"?
10-07-2019 02:01 PM
Hi,
I tested the same scenario for each of the 2 VIs and got almost the same results for each of the steps mentioned on my previous post.