LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Should "Reload for Each Call" unload after one call?

The subject line says it all, plus I asked the question here:  http://forums.ni.com/ni/board/message?board.id=170&thread.id=190669

 

I would like to use "Call Setup..." -> "Reload for Each Call" as an convenient way to optimize memory in my big application; however, LV isn't letting go of the dynamically called VIs.  Try running the attached examples with Profiler running and you'll see that only the only way to get the desired result is with "test LV7 dynamic call.vi".

 

Is there a way to coax the easy "Call Setup..." method into working?

 

Thanks

0 Kudos
Message 1 of 2
(2,866 Views)

Travis,

 

I ran all 3 of your VI's with the dynamic call to your 4th, but I added a for loop to them, so I could read data a little more easily form the profiler. I will attach a screenshot to see if you got similar results, but I changed the loop interations, and the memory was exactly the sam, only VI time changed.

 

test LV7 dynamic call: 31.49kB

test reload for each call: 31.30kB

test load with callers : 29.46kB

 

So, as you can see, the reload for each call DOES use less memory than the LV7 dynamic call, but load with callers uses even less.

 

I hope this helps you some.

Chris Van Horn
Applications Engineer
0 Kudos
Message 2 of 2
(2,835 Views)