Resource Tracking for FlightGear: Difference between revisions

Jump to navigation Jump to search
m
m (→‎Gallery: remove *thumb*)
Line 105: Line 105:
=== Thursday, August 27, 2015:  System Information Gatherer And Reporter (SIGAR) libraries adopted, new "sigar" sub-system ===
=== Thursday, August 27, 2015:  System Information Gatherer And Reporter (SIGAR) libraries adopted, new "sigar" sub-system ===


We decided to adopt the System Information Gatherer And Reporter (SIGAR) libraries, to provide cross-platform support for resource tracking, memory in addition to other new metrics(which are shown in the Gallery section of this article), are now exposed under the new sub-system "/sigar", which can be found in the property tree. VRAM support progress for other vendors are now postponed due to priority of Nasal and per-subsystem resource tracking. a development repository for the project is also being considered.
We decided to adopt the System Information Gatherer And Reporter (SIGAR) libraries, to provide cross-platform support for resource tracking, memory in addition to other new metrics(which are shown in the Gallery section of this article), are now exposed under the new sub-system "/sigar", which can be found in the property tree ('''sigar''' is also the name of the new subsystem, and both may be subject to change). VRAM support progress for other, non-nvidia, vendors are now postponed due to priority of Nasal and per-subsystem resource tracking, as well as issues involving non-proprietary drivers. A development repository for the project is also being considered. Fow the being, people wanting to test the latest patch, will need to clone the sigar repository and build/install the master branch (system-wide) and then rebuild fgfs using -DENABLE_SIGAR=ON


== Gallery ==
== Gallery ==

Navigation menu