20,741
edits
FlightGear benchmark: Difference between revisions
Jump to navigation
Jump to search
→Background
| Line 38: | Line 38: | ||
{{cquote|what about performance with different views (pilot view vs chase view), and having the panel open vs. closed in pilot view?<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40316.html|title=<nowiki>Re: [Flightgear-devel] Benchmark matrix</nowiki>|author=Saikrishna Arcot|date=Fri, 21 Jun 2013 14:08:11 -0700}}</ref>|Saikrishna Arcot}} | {{cquote|what about performance with different views (pilot view vs chase view), and having the panel open vs. closed in pilot view?<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40316.html|title=<nowiki>Re: [Flightgear-devel] Benchmark matrix</nowiki>|author=Saikrishna Arcot|date=Fri, 21 Jun 2013 14:08:11 -0700}}</ref>|Saikrishna Arcot}} | ||
A benchmark/regression testing suite could also be run through the [[FlightGear Build Server]]: | |||
{{cquote|A standardized benchmark would be, if we get enough data, be more of a general warning system - suppose we regularly monitor performance on 50 different systems, and after some commit we see 20% performance drop on 35 of them - that's indicate that the commit might be in some way problematic. But for this, we would require a regular time history - basically the monitoring script should run and report after every update of either FG or the drivers.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40318.html|title=<nowiki>Re: [Flightgear-devel] Benchmark matrix</nowiki>|author=Renk Thorsten|date=Sat, 22 Jun 2013 00:35:23 -0700}}</ref>|Renk Thorsten}} | |||
== Brainstorming == | == Brainstorming == | ||