20,741
edits
Resource Tracking for FlightGear: Difference between revisions
Jump to navigation
Jump to search
m
Resource Tracking for FlightGear (view source)
Revision as of 19:37, 22 February 2015
, 22 February 2015→Extending OSG StatsHandler: https://support.hyperic.com/display/SIGAR/Home
m (→NVIDIA) |
m (→Extending OSG StatsHandler: https://support.hyperic.com/display/SIGAR/Home) |
||
| Line 122: | Line 122: | ||
'''Stuart:'''I think 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. | '''Stuart:'''I think 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. | ||
== SIGAR == | |||
The [https://support.hyperic.com/display/SIGAR/Home Sigar API] provides a portable interface for gathering system information such as: | |||
* System memory, swap, cpu, load average, uptime, logins | |||
* Per-process memory, cpu, credential info, state, arguments, environment, open files | |||
* File system detection and metrics | |||
* Network interface detection, configuration info and metrics | |||
* TCP and UDP connection tables | |||
* Network route table | |||
This information is available in most operating systems, but each OS has their own way(s) providing it. | |||
SIGAR provides developers with one API to access this information regardless of the underlying platform. | |||
The core API is implemented in pure C | |||
== Extending OSG StatsHandler == | == Extending OSG StatsHandler == | ||