Resource Tracking for FlightGear: Difference between revisions

Resource Tracking for FlightGear (view source)

1,231 bytes added , 24 August 2015

20,741

edits

@@ Line 91: / Line 91: @@
 }}
 == Status ==
+A simple proof-of-concept is now working properly, while it is currently restricted to Linux-only OS for RAM tracking, and NVIDIA GPUs for VRAM tracking, the corresponding stubs for other operating systems and GPU vendors are prepared and waiting to be filled in over time. If you are interested in helping with this, you are invited to get involved - for the time being, it would help to have people involved with access to other operating systems (namely, Windows and Mac OSX), as well as different GPU makes (ATI/AMD and Intel primarily).
+People wanting to get involved, should ideally be able to patch & build FlightGear from source, so that we can exchange patches and integrate things step by step.
+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).
 == Gallery ==