Hackathon Proposal: Performance testing by replaying recordings

Title:	Performance testing by replaying recordings [[File: |thumbnail|]]
Potential mentors:	Julian Smith
Intro:	(short intro)
Interested Parties:	(feel free to add yourself)
Status:	Post-hackathon write-up (2021-11-7) See Performance testing by replaying recordings
Summary:	Create standardised rendering performance tests by replaying recordings.
Background:	Continuous recordings can record and replay the main window's size and the view (view type, direction, zoom), so replaying could be used to do standardised performance testing of the rendering code.
Details:	* Record various scenarios with main window position/size/view enabled (See File/Flight Recorder Control). Find a way to gather performance data when replaying a recording, e.g. average/stddev/worst-case frame-rate or frame-time. Make it easy to systematically replay recordings with replay of main window position/size/view enabled, and present performance data. Be able to test with different rendering settings. Store results so we can detect regressions, draw graphs etc. Also see: flightgear/flightgear/next/docs-mini/README-recordings.md
Ideas:
Required skills:
Learning Opportunities:
Notes:

References