04-13-2006 09:06 AM
04-13-2006 10:23 AM
04-13-2006 12:19 PM
Also remember that there is not always a good correlation between disk space and memory requirements consider the simple c code line
int bigArray[10000000];
This will take only a few Bytes of storage but will require a wopping MB of ram to run.
The runtime engine will require some memory but usually a large memory block is allocated for big arrays or dynamically growing data structures (which can be a sign of a memory leak). Also just because your program is small does not mean that you are not using several MB of dll calls.
Paul
04-14-2006 04:40 AM
Another example. Look at some .Net dlls. Amazingly small on disk but oohhh when they are loaded into memory!
@falkpl wrote:
Also remember that there is not always a good correlation between disk space and memory requirements consider the simple c code line
int bigArray[10000000];
This will take only a few Bytes of storage but will require a wopping MB of ram to run.
The runtime engine will require some memory but usually a large memory block is allocated for big arrays or dynamically growing data structures (which can be a sign of a memory leak). Also just because your program is small does not mean that you are not using several MB of dll calls.
04-20-2006 08:15 AM
Thank you all!
Yes,I build an empty vi to executable file.Run the program takes 22M memory.Maybe it is only for the run-time engine.
I try a login vi for initiation too.But only loading the run-time engine will take some time,not as fast as a ccode program.How can I quickly show a login page before the run-time engine loads and close the page automatically after the main vi runs?
Of course,I am not working for NI.I am only a graduate student.