> You can say THAT again! I wonder if OSG people know that they should > also throw out stuff from cache, not just put things in! > I have been bold enough to use the CACHE_ALL for today's TGA > multiplayer event ... at the end of the 6th hour or so, FG's memory > usage reached 7.5GB, with the extensive swapping negating any eventual > advantage of the caching. > > So, I certainly do not recommend setting this option on by default, > until the behavior is fixed (such as by introducing a memory limit).
I've got a stupid question - maybe someone who knows these things can educate me. If I do not use texture caching, textures are loaded from harddisk every time I need them, for each and every model. If I do use texture caching but my memory runs over, swapping takes place. Sometimes I may get lucky and the texture I need is currently in memory, sometimes it is on harddisk and needs to be loaded. Naively, it seems to me the second case is still faster than the first, because I always save at least some harddisk operations. I haven't flown for 6 hours straight with CACHE_ALL, but for two hours something, and it was still way faster than with CACHE_NONE. So, do I really lose anything here? Perhaps there's something I'm not seeing... Cheers, * Thorsten ------------------------------------------------------------------------------ Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
