> Maybe someone could do some tests when changing the setting > (SGPagedLOD.hxx:56) from "CACHE_NONE" to "CACHE_IMAGES" or even to > "CACHE_ALL" (then recompile/install sg+fg). Would be interesting to know > how this changed loading times, run-time fps and memory consumption.
I've just done a very quick test with a binary compiled with CACHE_ALL, and the result looks *very* promising. I've seen a 100x100 double-layer cloud config appear in the scenery less than 15 seconds - and that was while my second CPU was happily crunching some heavy numerics in the background, so there's some reason to expect it to be even better in reality. My previous binary with CACHE_NONE solved the same task under identical conditions in a bit more than 75 seconds. Quite possibly most of the time is now taken by setprop() statements writing into the /models/ section of the property tree (the time taken from the point where models start appearing in the scene is ~5 seconds) and by xml parsing. I'll investigate some more when I have more time and more free CPUs, but it seems that this is indeed what is needed. Cheers, * Thorsten ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
