From: Michael J. Lewis (mlewis++at++evl.uic.edu)
Date: 08/10/2001 16:09:20
What I found to be the most reliable in determining the current
amount of memory that you have is using amallinfo. However when deleting
a performer node, the memory reported from amallinfo does not go down.
But amallinfo is still very usefull in monitoring how close you are
getting to the PFSHARED limit point.
Also remember to do recursive deletions, so you can delete down the node
tree deleteing the pfGeosets of the node that you are deleting.
On Fri, 10 Aug 2001, [iso-8859-1] Jürgen Gotschlich wrote:
> Hello Mike,
>
> I've read the mails about memory consumption with great attention. I
> also have the problem of measuring the memory consumption of loaded
> files and textures.
>
> In my appl. I need to load/delete lots of files(geometry and textures)
> dynamically. So I always need to know how much memory is still available
> to load additional data or if I have to delete other portions first.
>
> Did you find a way to get that info ?
>
> Please let me know. Thanks.
>
> Jürgen
> --
> ________________________________________________________________________
>
> Jürgen Gotschlich email: juergen.gotschlich++at++dlr.de __/|_
> Phone: +49(531)295-3248/2778 /_/_/_/
> Fax : +49(531)295-2640 |/ DLR
>
> Deutsches Zentrum für Luft-und Raumfahrt | German Aerospace Center
> Institut für Flugsystemtechnik | Inst. of Flight Research
> Abt. Flugsimulation | Flight Simulation Dep.
> Lilienthalplatz 7 | Lilienthalplatz 7
> D-38108 Braunschweig | D-38108 Braunschweig, Germany
> ________________________________________________________________________
>
This archive was generated by hypermail 2b29 : Fri Aug 10 2001 - 16:08:16 PDT