MAME frameskip, throttle, speed, and refresh settings explained
Keep throttle on and speed at 1.0 for normal play, display the emulation-speed meter, and treat frameskip only as a way to reduce rendering work. Disabling throttle is a diagnostic for maximum throughput, not a fix; if the benchmark cannot exceed 100%, refresh and audio tweaks cannot create missing CPU capacity.
Do this in order
- 01
Record device, thermal state, MAME/core version, system short name, and current renderer, shader, frameskip, throttle, and speed settings.
- 02
Return to throttle on, speed 1.0, frameskip 0, and default audio/video; enable the emulation-speed display.
- 03
Run the same authorized scene long enough to observe stable speed and thermal behavior.
- 04
Use a no-throttle or benchmark run only to estimate available headroom, then restore normal throttling.
- 05
If the build is near 100%, test one small frameskip or remove one expensive shader; if far below, choose a lighter documented core or device.
- 06
Re-enable one feature at a time, verify audio and input, and save the result at game scope.
Decision and diagnostic table
| Control | What it changes | What it cannot prove |
|---|---|---|
| Frameskip | Drops some displayed frames to reduce render work | That emulated logic is accurate or CPU demand is solved |
| Throttle | Prevents running faster than original hardware | That the device has performance headroom |
| Speed factor | Changes the intended emulation-rate multiple | A legitimate performance repair at values other than 1.0 |
| Refresh speed / sync | Coordinates emulation with display timing | Extra CPU capacity when the core is far below target |
Emulation speed and displayed FPS are different
MAME can skip displayed frames while continuing to emulate machine time. A smoother speed percentage with frameskip may improve playability, but motion becomes less complete and the underlying driver workload remains.
Use the speed meter as the first performance signal. A 60 Hz screen does not guarantee that the emulated machine is sustaining its intended rate.
Throttle is a limiter, not an accelerator
With throttle enabled, MAME limits execution to the original machine’s rate. With it disabled, MAME runs as fast as the device allows, which is useful for estimating headroom but produces unnatural timing and audio.
Restore throttle for gameplay. A no-throttle result below target indicates that settings which only change synchronization cannot supply the missing compute capacity.
Change one cost at a time
Start by removing shaders, run-ahead, high internal resolution, and background work. Then test a conservative frameskip only if the core is close to full speed.
Record thermal conditions and retest after several minutes. A brief cold-device pass is not evidence of sustained Android performance.
Performance testing is not a reason to download a commercial benchmark ROM. Use your own lawful dump, creator-authorized content, or an original synthetic test.