Steve Baker (steve++at++mred.bgm.link.com)
Fri, 23 May 97 08:51:44 -0500
...I'm pretty sure you are right - with a similar application, we see
a similar behaviour.
For a long time we suspected a memory leak - but after fighting for
weeks to try to find one, we eventually realised that it was indeed
memory fragmentation.
I don't think there is a fix for this - except to add more memory.
We found that with memory fragmentation, the graph of memory-used
versus time is like this:
|
| *****************
| ********
| *****
| ***
| **
| *
|*
|
|
|_____________________________________
But with a memory leak, it tends to be more like this:
| *
| *
| *
| *
| *
| *
| *
|*
|
|
|_____________________________________
So, you can eventually work out how much RAM it will
ultimately consume.
We found that for a given visual range, you might eventually
double the amount of memory you initially need - and it
doesn't finally asymptote out to a stable amount of memory
until you had been flying around for perhaps 3 to 8 hours.
Steve Baker 817-619-1361 (Vox-Lab)
Hughes Training Inc. 817-619-8776 (Vox-Office/Vox-Mail)
2200 Arlington Downs Road 817-619-4028 (Fax)
Arlington, Texas. TX 76005-6171 Steve++at++MrEd.bgm.link.com (eMail)
http://www.hti.com (external) http://MrEd.bgm.link.com/staff/steve (intranet)
http://web2.airmail.net/sjbaker1 (external)
** Beware of Geeks bearing GIF's. **
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:17 PDT