20,741
edits
Resource Tracking for FlightGear: Difference between revisions
Jump to navigation
Jump to search
Resource Tracking for FlightGear (view source)
Revision as of 19:27, 23 August 2015
, 23 August 2015no edit summary
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
[[File:Patching-fg-3.2-to-make-more-subsystems-optional.png|450px|thumb|Screen shot showing a the performance monitor in a patched version of FlightGear 3.2 where subsystem initialization is made better configurable and increasingly optional by allowing subsystems to be explicitly disabled/enabled during startup. Decoupling internal subsystem dependencies means that we can more easily provide support for [[FlightGear Benchmark|benchmarking]], but also [[FlightGear Headless|headless]] regression testing - and eventually, also a standalone [[FGCanvas]] startup mode. This simplified startup mode results in roughly ~120 MB of savings in RAM. ]] | [[File:Patching-fg-3.2-to-make-more-subsystems-optional.png|450px|thumb|Screen shot showing a the performance monitor in a patched version of FlightGear 3.2 where subsystem initialization is made better configurable and increasingly optional by allowing subsystems to be explicitly disabled/enabled during startup. Decoupling internal subsystem dependencies means that we can more easily provide support for [[FlightGear Benchmark|benchmarking]], but also [[FlightGear Headless|headless]] regression testing - and eventually, also a standalone [[FGCanvas]] startup mode. This simplified startup mode results in roughly ~120 MB of savings in RAM. ]] | ||
--> | --> | ||
{{FGCquote|1= we want to avoid writing explicit deletes as much as possible, as that need is the source of most memory leaks. We have two classes for smart, referencecounted pointers, osg::ref_ptr and SGSharedPtr which should be used for all long-lived, shared objects. |2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=214289#p214289 | title = <nowiki>Re: How can I retire from the forum?</nowiki> | author = <nowiki>Tim Moore</nowiki> | date = Sat, 19 Jan 2008 02:40:21 -0800 }}}} | |||
{{FGCquote|1= it also opens up a larger question of how we do memory management in FG, and whether we should be doing things such as more aggressively freeing up terrain tiles. At one level, removing entire terrain tiles from memory earlier if memory occupancy becomes a concern would be a better management strategy than just stopping generating new buildings.|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=165125#p165125 | title = <nowiki>Re: Random Buildings</nowiki> | author = <nowiki>stuart</nowiki> | date = Aug 24th, 2012 }}}} | |||
{{FGCquote | {{FGCquote | ||