20,741
edits
FlightGear benchmark: Difference between revisions
Jump to navigation
Jump to search
m
→Objective
m (→Brainstorming: one step more towards benchmarking support in FG: https://gitorious.org/fg/fgdata/commit/67e625a81232b6282c7218418a6091a962567be8) |
m (→Objective) |
||
| Line 4: | Line 4: | ||
== Objective == | == Objective == | ||
{{Note|Based on [[Understanding Rembrandt|recent experiments]] with benchmarking [[Rembrandt]], it would obviously make sense to have access to individual stages (cameras)}} | |||
A long time ago, we once had a FG-specific benchmark suite called "FGBenchmark" over time this wasn't updated anylonger and got phased out- meanwhile, a number of end-users and long-term contributors have been talking about re-introducing a form of scriptable benchmark, directly as part of FlightGear itself, using [[Nasal]] scripting to recreate certain situations (location, aircraft, rendering settings etc) in order to gather runtime statistics, but also for better regression testing. | A long time ago, we once had a FG-specific benchmark suite called "FGBenchmark" over time this wasn't updated anylonger and got phased out- meanwhile, a number of end-users and long-term contributors have been talking about re-introducing a form of scriptable benchmark, directly as part of FlightGear itself, using [[Nasal]] scripting to recreate certain situations (location, aircraft, rendering settings etc) in order to gather runtime statistics, but also for better regression testing. | ||