Hi,Disabling optimization parameters (i.e. setting graphOpSeq to NULL in the 
SceneFileHandler::read() function) makes loading of OSB data faster in 
OpenSG.However I made some observations regarding data loading in Optimizer 
( with opviewer) and OpenSG :  o If loading some dataset (in CSB format) in 
opviewer for the first time     takes X secs then subsequent loading of the 
same data takes about     X/10 seconds i.e. loading the same data second 
time onwards is     considerably faster.  o Loading same dataset (converted 
to OSB) in osg application takes    around same time always i.e. first and 
second time loading times    don't differ.[ The datasets I tried were 
"Dragon" and "Happy Buddha" from 
http://www-static.cc.gatech.edu/projects/large_models/converted to CSB and 
OSB for loading into opviewer and OpenSG application respectively. ]Does 
anybody has any clue about this behaviour with opviewer ?  Thanks,- 
Vaibhav>That said, OSB in general loads very fast. The only thing I can 
think of>that might slow things down is that by default some basic 
optimizations>(striping etc.) are run on every loaded model. You can 
deactivate (or>change) that by giving an optional parameter 
to>SceneFileHandler::read(). That parameter is the GraphOpSequence to be>run 
after loaded, or NULL.>How much of a difference are we talking here anyway? 
10% or a factor of>10?>Hope it helps>Dirk 



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to