Hi Nick, I am curious whether this slowdown is due to CPU work (scanning shader maps and selecting used ones) or GPU work (shaders are recompiled or linked too often). Do you have any profiling data to share ?
I do expect some performance degredation while using it vs standard osg::program. Thats related to active shader selection process in Virtual::Program apply. I expect this could become nasty when one uses a lot of virtual programs with many shader changing frequently. Lets say that VirtualProgram in current candidate release was mainly intended as working functional prototype. I expected that implementing this functionality in target osg version would also require some modifications and optimizations to program state handling and few modifications to speed it up by caching last used set of shaders and programs. Cheers, Wojtek ----- Original Message ----- From: Trajce Nikolov To: OpenSceneGraph Users Sent: Friday, February 12, 2010 10:30 AM Subject: [osg-users] osgCandidate::VirtualProgram performance Hi, I am using this in my app and facing really performance problems. When I replace it with osg::Program and Shaders, it is a huge difference. Like from 30Hz to 100Hz. Any ideas why it is so slow ? -Nick ------------------------------------------------------------------------------ _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
