Re: [osg-users] New defaults in DatabasePager, please test

2010-11-05 Thread Alexandre Amalric
Hi Robert, I am wondering why there is no way to remove PagedLod child wich are visited by the culling but wich are also out of range from the camera. Here is a simple case let's image I have 100 PagedLod each composed from a low poly internal model and a high res external model (displayed when

Re: [osg-users] New defaults in DatabasePager, please test

2010-11-05 Thread Robert Osfield
Hi Alex, The DatabasePager already has a scheme for load balancing and will automatically expiry PageLOD's that are out of range. It only does the expiry once a user specified maximum number of PageLOD's is reached, while the default is set to 500, but you could set this to 1 if you wanted and

Re: [osg-users] New defaults in DatabasePager, please test

2010-11-05 Thread Alexandre Amalric
Hi Robert, I'm using osg 2.8.3 and it seems it's not the case. To continue with this sample, let's imagine I set the _targetMaximumNumberOfPageLOD to 20, in capped_removeExpiredSubgraphs if the camera is looking to those 100 PagedLod at the same time the _inactivePagedLODList is empty and the

Re: [osg-users] New defaults in DatabasePager, please test

2010-11-05 Thread Robert Osfield
Hi Alex, I've got too many things on to try and get my head around your understand of some code that has already been modified in svn/trunk. In svn/trunk and the 2.9.x series the DatabasePager has been improved further, so go test there. Robert. On Fri, Nov 5, 2010 at 10:32 AM, Alexandre

Re: [osg-users] New defaults in DatabasePager, please test

2010-11-05 Thread Alexandre Amalric
Hi Robert, Reviewing the latest snv code from the databasepager, the problem remains the same. The only expired nodes the databasepager is removing are the one wich are in the inactivePagedLODList this one is only filled with node that hasn't been traversed for a while (compare

Re: [osg-users] New defaults in DatabasePager, please test

2010-11-05 Thread Robert Osfield
Hi Alex, Just because children of a PagedLOD may be out of range doesn't mean that the PageLOD itself isn't required in memory, if the cull traversal is hitting the PagedLOD it's active an really can't be expired, even if the children are being culled at that point in time. I rather feel that

Re: [osg-users] New defaults in DatabasePager, please test

2008-12-15 Thread Glenn Waldron
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. Glenn Waldron : Pelican Mapping : http://pelicanmapping.com : +1.703.652.4791 On Mon, Dec 15, 2008 at 9:40

Re: [osg-users] New defaults in DatabasePager, please test

2008-12-15 Thread Robert Osfield
Hi Glenn, On Mon, Dec 15, 2008 at 3:07 PM, Glenn Waldron gwald...@gmail.com 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

[osg-users] New defaults in DatabasePager, please test

2008-12-15 Thread Robert Osfield
Hi All, A month of so back I developed a new expiry scheme for DatabasePager that works to ensure that number of PagedLOD in memory at any one time does not exceed a specified target maximum number of PagedLOD. The new scheme allows the number of PagedLOD in memory to raise until it hits the