From: Aron Bartle (abartle++at++de-solutions.com)
Date: 04/19/2000 14:38:29
Hello,
I'm wondering if anybody has a theory why a node saved & restored as a
.pfb via pfdSaveFile/pfdLoadFile would occupy MORE MEMORY after
restored?
o First, the app. generates some geometry, and saves it to multiple .pfb
files.
o The app is then restarted such that it loads the .pfb files instead of
generating the geometry from scratch.
o File saving/loading takes place in the APP process
o I tried to optimize restored nodes with pfdMakeShared,
pfdCombineLayers, pfdCleanTree to no effect.
The pfMemory usage from the restored nodes appears to be TWICE!! (?)
that of the memory usage from the constructed node. Sorry I don't have
any "hard" numbers yet, but dang if it ain't using much more memory!
The verboseiest scenegraphs are identical save for (obviously) memory
addresses and:
< Modified mask: 0x9202
--- > Modified mask: 0x1202< SHADEMODEL: PFSM_GOURAUD --- > SHADEMODEL: Inherited
Where "<" is the generated geometry and ">" is the .pfb-file-loaded geometry.
Human nature being what it is (i.e. "blame the other guy" ;-) I might guess that pfdLoadFile is leaky, or over-allocating memory for vertices/colors that don't exist. Some smart performer out there please set me straight!
Thanks,
-Aron
-- Aron D. Bartle, Software Architect abartle++at++de-solutions.com 757.858.2800
This archive was generated by hypermail 2b29 : Wed Apr 19 2000 - 14:28:31 PDT