20060106: Problem loading certian model displays with Fedora Core 4 (foo.out file)

>From: Jacob <address@hidden>
>Organization: 
>Keywords: 200601062238.k06Mcq7s001762 IDV memory

Hi Jacob-

>       I just wanted to mention one thing also about the memory build up from
>loading 3 or 4 different data displays in IDV.  When I would of course
>load a 5 image loop of the GOES-East 10.7 um IR CONUS, the memory status
>in the lower right corner of the screen would go up to about 134 MB.
>Well, then I would load a couple of other displays, like water vapor,
>radar, etc.  When I add on these displays, the memory status increases
>to about 361 MB.  Then I wanted to see what would happen if I loaded a
>display on top of all that which would increase that memory status only
>a slight bit, so I loaded a NEXRAD 5-image loop of Raleigh, NC.  When I
>went to create the display for the NEXRAD image loop, which would
>increase the memory usage only a small bit from 361 MB, IDV shut down
>and the program terminated.  When I looked at the terminal window from
>where I loaded the IDV, there was one line added which said:
>
> ./runIDV: line 24: 17388 Killed                  ./jre/bin/${command}

How much swap space do you have on that machine?  I've seen the
IDV become sluggish when it reaches the point where it has to
swap memory, but I haven't seen it crash.

>       Would this have anything to do with our problem with trying to display
>the 3D models?  I thought it was interesting for this to happen.  Could
>this be a sign that IDV will only allow a limited amount of memory
>usage?  When I used IDV on Windows XP, it would allow me to go all the
>way up to 530 MB.  I had 512 MB of RAM, which is the same amount of
>memory I have on this computer, running Fedora Core 4.
>       Thank you again for all of your help and support.  God Bless.

If you only have 512 Mb of memory on the system, I would suggest
editing the runIDV script and lowering the amount of memory that
the IDV is using as I described in a previous e-mail.  You could
change:

command="java -Xmx512m -jar idv.jar $*"

to be:

command="java -Xmx300m -jar idv.jar $*"

You could experiment with the number that gives you the best 
performance.  

Don Murray
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.