20,741
edits
FlightGear benchmark: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
{{FGCquote | {{FGCquote | ||
|1= a thing FlightGear developers could do to help developers of the free drivers, to help themselves, to help users and to help the Phoronix website would be to implement a benchmark mode. Phoronix is desperate to find more up to date and graphically challenging games for their benchmarks. The driver developers do read Phoronix and use the Phoronix benchmark suite to optimie the drivers. Users make buying decisions based on these benchmarks and general reports and last but not least, you know best how difficult performance optimization is for an application developer. | |1= a thing FlightGear developers could do to help developers of the free drivers, to help themselves, to help users and to help the Phoronix website would be to implement a benchmark mode. Phoronix is desperate to find more up to date and graphically challenging games for their benchmarks. The driver developers do read Phoronix and use the Phoronix benchmark suite to optimie the drivers. Users make buying decisions based on these benchmarks and general reports and last but not least, you know best how difficult performance optimization is for an application developer. | ||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/31904511/ | |||
| title = <nowiki>Re: [Flightgear-devel] Graphics cards</nowiki> | |||
| author = <nowiki>Stefan Seifert</nowiki> | |||
| date = Jan 30th, 2014 | |||
| added = Jan 30th, 2014 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= I played around with the existing capabilities last weekend and it looks like we're almost there anyway. Setting FG_HOME to a temporary directoy ought to be enough to prevent leaking settings from one run to another and allows using specific settings for the benchmark run (e.g. Rembrandt/ALS). Using generic file input allows replaying a full flight and the telnet interface allows reading FPS and frame distance numbers. The script at https://github.com/flighten/test attempts to do so anyway. Combined with some static weather input and fixed random seeds (probably supplied on the command line) we'd have all we need for reproducible benchmarks. If any developer finds some time to implement the missing pieces this could help tremendously. My personal situation will improve in about half a year, but if someone can pull this off before that, we'd not only get better support but also great marketing. FlightGear would very probably be featured in every Phoronix benchmarking article and those are very frequent. | |||
|2= {{cite web | |2= {{cite web | ||
| url = http://sourceforge.net/p/flightgear/mailman/message/31904511/ | | url = http://sourceforge.net/p/flightgear/mailman/message/31904511/ | ||