272
edits
Resource Tracking for FlightGear: Difference between revisions
Jump to navigation
Jump to search
Resource Tracking for FlightGear (view source)
Revision as of 21:04, 27 August 2015
, 27 August 2015→Status: Thursday, August 27, 2015
Hamzaalloush (talk | contribs) (→Status: Thursday, August 27, 2015) |
|||
| Line 102: | Line 102: | ||
Using the "GL_NVX_gpu_memory_info" extension from Nvidia's OpenGL API, [[User:Hooray|Hooray]] has been able to expose video memory information, which was tested initially on a GT540 mobile edition card successfully. In an effort to make this extendible for other GPU's, we inherit a GPUInfo object for each vendor's implementation. Testing for other GPU's will be required in the future. | Using the "GL_NVX_gpu_memory_info" extension from Nvidia's OpenGL API, [[User:Hooray|Hooray]] has been able to expose video memory information, which was tested initially on a GT540 mobile edition card successfully. In an effort to make this extendible for other GPU's, we inherit a GPUInfo object for each vendor's implementation. Testing for other GPU's will be required in the future. | ||
=== Thursday, August 27, 2015: System Information Gatherer And Reporter (SIGAR) libraries adopted, new "stats" 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 "/stats", 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. | |||
== Gallery == | == Gallery == | ||