mirror of
https://github.com/dosbox-staging/dosbox-staging
synced 2025-12-04 16:27:29 -05:00
Page:
Performance tests
Pages
AUTOTYPE candidates
Adding utilities
Application issues
Applications
Audio configuration recommendations
Audio mixer signal flow diagram
Audio tests
Building on NixOS
CPU tests
Config file examples
Controller issues
Creative 4MB GMGSMT
DOS 32A compatibility list
DOS ROM format
DOS filesystem tests
DOS tests
DOSBox forks
Documentation (unmaintained)
Dual OPL2 and OPL3 games
Dual mouse gaming
Frequently asked questions
Game controls guide
Game issues
Games with CD DA, GUS and MIDI audio
Games with enhanced Tandy & PCjr graphics and sound
General dev notes & tips
Getting started
Gravis UltraSound enhancements
Home
Input tests
Instant launch
Intel compiler tips
Joysticks
Keymapper
Learning DOS programming
MIDI
Multiplayer & serial ports
Performance tests
Release process
Running games from batch files
Shaders
Shortcuts
Sound cards
Sound issues
Sourceport links of classic DOS first person shooters
Special keys
Tips & tricks
True 16 bit audio games
UniVBE
Video cards
Video tests — CRT shaders
Video tests — Presentation
Video tests — Video modes
Windows 1.0x
Windows 2.x
Windows 3.0
Windows 3.1x
Windows 9x
Windows
Working with disc images on Windows 3.x
No results
10
Performance tests
John Novak edited this page 2025-07-31 17:52:49 +10:00
Table of Contents
Performance tests
We should run the tests on this page periodically, at least once at the end of each release cycle, to guard against regressions.
Pay attention to the following when running performance tests:
- Make sure you're not doing anything resource-intensive in the background (e.g., downloading large files, copying files to an USB drive, performing OS updates or virus scans, running games or anything performance-intensive, including browsers with many tabs open, etc.)
- Run the tests at least three times and take the best result.
- If using a laptop, connect it to the power adapter to prevent it from entering "energy saver" mode.
- Display resolution (e.g., 1080p vs 4K display) has a large effect on performance, even if the rest of the system is identical.
- This should be fairly obvious, but use the same system if possible for regression testing, using the same desktop resolution.
Quake benchmark
This is our standard benchmark to guard against performance regressions. The Quake benchmark is the best tool for the job as it is one of the most demanding DOS programs, and it can scale to pretty much any CPU speed (even up to Pentium 4 speeds), so the bottleneck will always be the emulator. Always use the included configuration to ensure comparable results.
General
How-to's
- Adding utilities
- Applications
- Config file examples
- Dual-mouse gaming
- Getting started
- Instant launch
- Joysticks and Gamepads
- Keymapper
- Multiplayer & serial ports
- Windows
Lists
- AUTOTYPE candidates
- CDDA / GUS / MIDI games
- DOS/32A compatibility
- Dual OPL2 and OPL3 games
- Games with enhanced Tandy & PCjr graphics and sound
- Shaders
- Special keys
Audio
- Audio mixer signal flow diagram
- Audio configuration recommendations
- GUS enhancements
- MIDI
- Sound cards
- True 16-bit audio games
Video
Issues
Dev
- How to contribute
- Release process
- Audio tests
- CPU tests
- DOS tests
- Input tests
- Performance tests
- Video tests — Video modes
- Video tests — CRT shaders
- Video tests — Presentation
- Learning DOS programming
- Intel compiler tips