08-15-2007 11:04 AM
08-15-2007 12:13 PM
08-15-2007 02:53 PM
While loops with no delay cause a race condition that consumes RAM
try adding a small delay in your while loop
use the wait(ms) vi even a 1 ms delay will improve performance
08-15-2007 03:13 PM - edited 08-15-2007 03:13 PM
"While loops with no delay cause a race condition that consumes RAM"
Message Edited by smercurio_fc on 08-15-2007 03:13 PM
Message Edited by smercurio_fc on 08-15-2007 03:14 PM
08-15-2007 05:46 PM
11-26-2014 05:52 AM
Hi,
I am sorry but I don't know how to create a new discussion. That's why i am trying to solve it by this way. I also have a RAM consumption problem. Is there any possiblity to find the RAM consumer? I would like to know the RAM consumption in detail, like for the constant A x kB and for the 2-dimensional array M y kB and for the writing process z kB.
11-26-2014 06:19 AM
Please go through the Quick intro to start using the forum.
11-26-2014 09:47 AM
@dqp wrote:
Hi,
I am sorry but I don't know how to create a new discussion. That's why i am trying to solve it by this way. I also have a RAM consumption problem. Is there any possiblity to find the RAM consumer? I would like to know the RAM consumption in detail, like for the constant A x kB and for the 2-dimensional array M y kB and for the writing process z kB.
Tools -> Performance -> VIs and memory
/Y
11-26-2014
11:52 AM
- last edited on
03-27-2025
09:20 AM
by
Content Cleaner
dqp wrote:I am sorry but I don't know how to create a new discussion. That's why i am trying to solve it by this way. I also have a RAM consumption problem. Is there any possiblity to find the RAM consumer? I would like to know the RAM consumption in detail, like for the constant A x kB and for the 2-dimensional array M y kB and for the writing process z kB.
Please try to start a new discussion following the instructions by P@Anand.
The RAM consumption for arrays can be easily calculated from the number of elements in the array and the datatype of the elements. In addition, arrays need to be contiguous in memory, meaning that constantly resizing arrays in memory will cause frequence reallocations and memory fragmentation, at which time you might not have enough contiguous ram left. You can run out of memory earlier than you think. Remember that indicators and transfer buffers contain additional datacopies. Overuse of local variables and value property nodes can force additional copies in memory and should thus be avoided.
There are many programming tools that can accumulate evergrowing data forever and can thus cause memory issues (building array in shift registers, build xy graph express VI configured to retain data, etc. etc.)
Profiling gives you the memory use of each subVI and might not point out the data structure that is responsible. It would be easiest if you could post your VI. A lot of experts here in the forum can probably point out memory inefficient code very quickly by just looking at it.
If you have the execution trace toolkit, that caould also help analyze memory issues.
In summary: