From: Don Tidrow (dtidrow++at++nvl.army.mil)
Date: 06/20/2001 17:11:18
Our application creates and deletes numerous pfObjects, based on where the view
is and how far it can see. As a result, the main pfSharedArena seems to be
fragmenting pretty badly - at least, that's the guess I have (the app
somtimes dies with an insufficient memory error, even though amallinfo says
there's plenty). Are there any parameters I can tweak to reduce the
fragmentation problem (if that's what it is)? I've been playing with amallopt,
but it's not very clear from the man pages how it affects the pfArena.
Here's the current amallopt() calls I'm making:
amallopt(M_FREEHD, 1, pfGetSharedArena());
amallopt(M_MXCHK, 10000000, pfGetSharedArena());
amallopt(M_MXFAST, 1024, pfGetSharedArena()); // changed this first
amallopt(M_GRAIN, 16, pfGetSharedArena());
amallopt(M_BLKSZ, 262144, pfGetSharedArena());
Hints, tips, anyone?
Don
-- "If Java had true garbage collection, most programs would delete themselves upon execution." - Robert Sewell-------------------------------------------- | Don Tidrow | | Visual Simulation Developer | | US Army CECOM-NVESD | | ph: (703)704-1361 fax: (703)704-1753 | --------------------------------------------
This archive was generated by hypermail 2b29 : Wed Jun 20 2001 - 17:09:25 PDT