Hi All, I was hoping to leave serious stats work for a week or two, but am finding that I need it myself for doing benchmarking and profiling of different shadow volume codes. So tomorrow I'll spend some time putting a bit of a stats collecting framework together in both the core osg, and osgViewer. Timing Stats collection is just one thing though.
The next issue is how do you present the results and there is huge scope for different ways of recording, presenting and using the timing stats. The osgProducer::Viewer had one take on how to present the results, this needn't be the be all and end all - I'm open to suggestions on useful ways of reporting the results - both graphically and recording it. Timing stats are really about finding bottlenecks and this can be quite an involved process - the stats osgProducer::Viewer displayed were useful, but often not fine grained enough. More fine grained reported isn't something you can do with a general purpose high level stats collection and reporting - its needs some means for extending the basics stats collection with your own extras and how to report these extras. I can image this getting quite complex so I thought I'd bend your ears for what schemes you've seen used before and found really effective. With that call for thoughts I'll turn in for the night :-) Robert. _______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
