Small program occupying lots of memory

[Jack123]

I wrote a small program (attached). It is not a big program, however it is occupying 9.7MB of memory.

Can any one help how to reduce the memory or what is the issue in the program.

Thanks

Jack

[crossrulz]

How large are those arrays?  That would be the first thing I would look at for being a memory hog.

[KoenR94]

Is it possible you have big pictures in your frontpanel?

Also try clean up the wire mess, just a tip.

[Jack123]

The Y array and circ are  800x800.

[KoenR94]

I don't think 800x800 arrays are the problem, the both will take 16kb.

Probably it's an image or some other file.

[GerdW]

Hi Jack,

attach the VI instead of a plain picture of the BD!

@Koen:

an "Image" with 800×800 pixels provided as DBL datatype requires 800×800×8 bytes = 5000 KiB in memory. With some overhead (read: "data copy"!) the VI easily needs 9.7MB of RAM...

[GuenterMueller]

Right you are Gerd.

Keep in mind that Jack123 mentioned that both arrays ("The Y array and circ are  800x800.") are 800 x 800 with datatype DBL.  A memory footprint of 9,7MB is as expected: 800 x 800 x 8 = 10240000 bytes.   10240000 bytes / 1.024 / 1.024 = 9.765 MB

[KoenR94]

Thanks GerdW got juked by Labview compression.

If you make an array with many duplicates its waaaaay smaller.

Next time I'll think first before trying!

[altenbach]

---

@Jack123 wrote:

I wrote a small program (attached). It is not a big program, however it is occupying 9.7MB of memory.

Can any one help how to reduce the memory or what is the issue in the program.

---

If the arrays are 800x800, that sounds about right. Actually I would probably expect more than that.

The I32 array will be about 2.5MB (800x800x4) bytes and the DBL array about 5MB (800x800x8, assuming "circ" is also 800x800). Is this a subVI that has the front panel hidden? If the front panel is open, you also have extra data copies in the controls and indicators. There are several coercion dots, forcing additional data copies. How big is "image pix value"? How big is "Phase"? I expect more than 10MB total for this VI! Then we have "image" and "image out"

How are you measuring the memory use?

To optimize memory use, first you need to clean up the code. Why is "image pix value" control inside the FOR loop? Do you expect it to be modified during the execution of the loop? If you don't, it seems silly to recalculate the min-max on the same array 24 times in a row. A large part of the loop code is loop invariant. (the compiler might be able to move most of it outside the loop, but it is difficult to predict what it will do, especially if debugging is enabled.

Keep the front panel of the subVI closed. Disable debugging., etc.

Can you attach your VI?

[crossrulz]

---

@altenbach wrote:

---

@Jack123 wrote:

I wrote a small program (attached). It is not a big program, however it is occupying 9.7MB of memory.

Can any one help how to reduce the memory or what is the issue in the program.

---

If the arrays are 800x800, that sounds about right. Actually I would probably expect more than that.

The I32 array will be about 2.5MB (800x800x4) bytes and the DBL array about 5MB (800x800x8, assuming "circ" is also 800x800). Is this a subVI that has the front panel hidden? If the front panel is open, you also have extra data copies in the controls and indicators. There are several coercion dots, forcing additional data copies. How big is "image pix value"? How big is "Phase"? I expect more than 10MB total for this VI! Then we have "image" and "image out"

---

Christian, look at the VI again.  Y is a 2D array of doubles, along with circ.  We can't actually tell what the blue 2D array's data type is based on the picture (data type is defined with a constant).

Are we talking about actual memory (RAM) or the space on disk?  9.7MB makes perfect sense for space on disk since 800*800*8*2 gives us 9.7MB.  Are those controls supposed to hold default values?  If not, empty the arrays (right-click on the front panel controls and choose Data Operations->Empty Array) and then save values as the default.