LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

system low on virtual memory

I will not argue with good programming techniques and style.

I agree!

But...

She said it worked OK when run as "scaled down",
and,
only has 128Meg of memory.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 11 of 13
(735 Views)
Hi, thanks for all the good advices. I can't preallocate the array because I don't know how many items will be in the array. It's based on what the user input, base on how many temperature and voltages they want to run the test over. I pull up task manager and the CPU usage when I ran 1/3 of the input file and it is 100% most of the time, memory usage is 270096K, physical memory is 129252 K and I have 16340K left. Is there a way that I can dump this data to a temporary text file, to a physical memory, then read it back in the end? In visual basics, Java, and C, there is a routine that you can write to the hard drive, and then read it back in the end. Is there something like that in LabView? I have looked at my code and it's
as most efficient as I can make it. If you run the VI server to call subVI A, and if there are some subVI's in subVI A that you don't use, is it a better idea to remove the subVI's inside of subVI A. The reason that I am asking this is because I don't want to remove the excel and html subVI inside of subVI A, just in case the user want to just run subVI A directly by itself, and not go through the main VI interface. Thanks again.
0 Kudos
Message 12 of 13
(735 Views)
Hi Ann,

I think it is time for you to post some new questions!

First, 512 Meg of memory and this whole thing becomes a non-issue!

Re:your two follow-up questions. I suggest you post two follow-up questions. One Question re: saving data while you run. Yes it is possible, I do it all of the time, but this warrents a diferent thread. Similarly with the dynamic call question of sub-VI's.

The reason I am asking you to post new Q's is;
1) Many Enthusiats who may know the answer to your questions may not be watching a thread this deep. You can get a wider audience.
2)People searching for answers to Q's like your follow-ups, will probably chase down a Q with what you started.

So...
Get more memory,
Post more qu
estions,
Be patiant with us, we are mostly just volunteers.

Trying to help,

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 13 of 13
(735 Views)