20,741
edits
Resource Tracking for FlightGear: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
[[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 | |||
|In general I’d rather not see any raw pointers as class members unless they are truly weakly-referenced, and in that case I’d prefer they were to an SGReferenced via SGWeakPtr.<br/> | |||
<br/> | |||
BTW for C++11 folks I’m aware auto_ptr will go away but that should be a search-and-replace refactoring. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/34113349/ | |||
|title=<nowiki>Re: [Flightgear-devel] Major problems with the AI traffic system</nowiki> | |||
|author=<nowiki>James Turner</nowiki> | |||
|date=<nowiki>2015-05-14</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote | ||
|3.2 switched the base-package scenery to the high-resolution (i.e. memory-intensive) version, with the result that FG on default settings hangs my system (4GB memory, Intel graphics, no swap). | |3.2 switched the base-package scenery to the high-resolution (i.e. memory-intensive) version, with the result that FG on default settings hangs my system (4GB memory, Intel graphics, no swap). | ||