Hi Glenn, On Mon, Dec 15, 2008 at 3:07 PM, Glenn Waldron <[email protected]> wrote: > Robert, one quick clarification: does the new max-PagedLOD scheme work in > conjunction with expiry settings, or are they mutually exclusive techniques? > I have not studied the new code yet.
The new TargetMaximumNumberOfPageLOD scheme replaces the other expiry delay/expriy frames one(s), all the setting for the later techniques have no effect when the TargetMaximumNumberOfPageLOD has an non zero value. My plan is to phase out the old expiry code, but won't do this for 2.8, we need to roll out the new code and make sure it's working well across the full spectrum of usage models before we starting removing the older code. My current belief is that the new scheme is just much more robust at load balance than the previous ones that there is little reason to carry the old ones long term. If applications won't to change their memory needs at runtime then can always increase and lower the target maximum number of PagedLOD at their own choosing. If thing looks good for the new scheme once 2.8 rolls out I'll remove the back end code for the old algorithms then just issue a warnings when users try to use the setExpiryDelay/ExpiryFrames, then finally remove the set methods completely as well. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
