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 10:14, 24 August 2015
, 24 August 2015→Status
(→Status) |
(→Status) |
||
| Line 96: | Line 96: | ||
The mid-term idea here being to expose relevant system metrics to the FlightGear property tree, so that these can be internally used for benchmarking/feature-scaling purposes, but also for regression testing - for instance, any metrics exposed to the property tree can be trivially accessed using built-in means, such as [[Logging properties]] (CSV), which would in turn make it possible to create diagrams using gnuplot for different startup/run-time configuration (think minimal startup profile or Rembrandt vs. ALS etc). | The mid-term idea here being to expose relevant system metrics to the FlightGear property tree, so that these can be internally used for benchmarking/feature-scaling purposes, but also for regression testing - for instance, any metrics exposed to the property tree can be trivially accessed using built-in means, such as [[Logging properties]] (CSV), which would in turn make it possible to create diagrams using gnuplot for different startup/run-time configuration (think minimal startup profile or Rembrandt vs. ALS etc). | ||
At some point, we're also hoping to leverage off the patches from [[Initializing Nasal early]] to determine how much individul subsystems are adding to overall RAM/VRAM load during initialization, and especially during [[Reset & re-init]]. | |||
== Gallery == | == Gallery == | ||