20,741
edits
Howto:Optimizing FlightGear for mobile devices: Difference between revisions
Jump to navigation
Jump to search
Howto:Optimizing FlightGear for mobile devices (view source)
Revision as of 10:20, 5 August 2012
, 5 August 2012→Tracking Memory Utilization at the Subsystem-level
| Line 198: | Line 198: | ||
* [http://gitorious.org/fg/simgear/commit/27a1c02/diffs SimGear commit] | * [http://gitorious.org/fg/simgear/commit/27a1c02/diffs SimGear commit] | ||
* [https://gitorious.org/fg/flightgear/commit/4b2506d/diffs FlightGear commit] | * [https://gitorious.org/fg/flightgear/commit/4b2506d/diffs FlightGear commit] | ||
The performance monitor dialog reads all data from the property tree and it is created dynamically using a Nasal module in [http://gitorious.org/fg/fgdata/blobs/master/Nasal/performance_monitor/monitor.nas $FG_ROOT/Nasal/performance_monitor/monitor.nas] | |||
It would probably suffice to use "placement new" (i.e. pool memory) here, and overload the new operator at the SGSubsystem level (i.e. in SimGear), so that all subsystems use the overloaded new operator automatically. This would allow us to keep track of the number of memory allocations per subsystem, and also the amount of total RAM allocated by single subsystems. In addition, we could also track freeing via delete, too. And publish all the info to the property tree. | It would probably suffice to use "placement new" (i.e. pool memory) here, and overload the new operator at the SGSubsystem level (i.e. in SimGear), so that all subsystems use the overloaded new operator automatically. This would allow us to keep track of the number of memory allocations per subsystem, and also the amount of total RAM allocated by single subsystems. In addition, we could also track freeing via delete, too. And publish all the info to the property tree. | ||