A discussion came up this week about the overhead and memory consumption of various OSG objects, relating to the possible indiscriminate use of them. It turned out not to be an issue, but in the process of investigating, I quickly measured the in-memory byte sizes of a few common OSG objects. These are simply measured with sizeof(osg::Node) or the like. Obviously, in practical use, the containers and ref_ptrs involved increase the actual memory consumption, but this gives you a baseline idea.
Compiler is MSVC++ 2005, Win32: Release Node: 160 Group: 176 Switch: 200 LOD: 216 PagedLOD: 276 Geode: 200 Geometry: 308 Drawable: 172 StateSet: 192 Debug Node: 172 Group: 192 Switch: 224 LOD: 236 PagedLOD: 304 Geode: 216 Geometry: 332 Drawable: 184 StateSet: 260 Thought it might be informative to someone else, so here it is. -- Chris 'Xenon' Hanson, omo sanza lettere Xenon AlphaPixel.com PixelSense Landsat processing now available! http://www.alphapixel.com/demos/ "There is no Truth. There is only Perception. To Perceive is to Exist." - Xen _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
