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 14:43, 16 August 2014
, 16 August 2014→Problem
| Line 36: | Line 36: | ||
* http://forum.flightgear.org/viewtopic.php?f=4&t=21870&p=199379#p199379 | * http://forum.flightgear.org/viewtopic.php?f=4&t=21870&p=199379#p199379 | ||
{{FGCquote | |||
|Fast forward 2 years later, there are now several options available to query the OS/GPU driver and obtain GPU specific information, such as amount of dedicated VRAM and overall GPU/VRAM utilization - here's what I've found for nvidia, and I am willing to provide a corresponding patch to expose these stats to the property tree and update them, i.e. once or twice per second:<br/> | |||
<br/> | |||
[http://www.geeks3d.com/20100531/programming-tips-how-to-know-the-graphics-memory-size-and-usage-in-opengl/ http://www.geeks3d.com/20100531/program ... in-opengl/] | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=216763#p216763 | |||
|title=<nowiki>Re: Open GL - out of memory error.</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sat Aug 16</nowiki> | |||
}} | |||
}} | |||
== Problem == | == Problem == | ||
It would be great to write subsystem-specific RAM usage info to the property tree, so that it can be shown (i.e. in the performance monitor), but also used by Nasal scripts to scale down features dynamically - the degree of swap usage vs. amount of free RAM is probably one of the most important metrics here. | It would be great to write subsystem-specific RAM usage info to the property tree, so that it can be shown (i.e. in the performance monitor), but also used by Nasal scripts to scale down features dynamically - the degree of swap usage vs. amount of free RAM is probably one of the most important metrics here. | ||