Hi Vaibhav,
Vaibhav Saxena wrote:
>
> Thanks Dirk for your suggestion.
>
> Disabling optimization parameters (i.e. setting graphOpSeq to NULL in the
> SceneFileHandler::read() function) makes loading of OSB data faster in
> OpenSG.
OK, good. Not unexpected, but good. ;)
>
> 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 ?
Usually that effect is because of caching, i.e. the second time it will
be loaded from the memory cache, which is obviously faster than the
disc. But we see the same effect in our applications, not sure why you
don't see it. Was something else chewing up memory when you were testing
OpenSG?
In any case, the test has limited expressive value, as how many times do
you load the same dataset in a row? Usually you load it once and start
working. ;)
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
