Engineering

The Boring Tech Behind 120 FPS

Object pooling, draw-call budgets and why our rendering thread goes to sleep more than yours. A frank engineering post about the unglamorous decisions that keep frames flat.

By M. Chen — Engine Lead 11 Sep 2026 14 min read
Frame profiler — flat line
Players never notice the frames we didn't draw. That's the entire job.
M. Chen — Engine Lead
Memory map — 38MB ceiling

Engine Numbers

Frame budget at 120fps8.3ms
Peak memory footprint38MB
Cold start to first ignition0.6s
Key Takeaways

If You Only Remember Three Things

1

120fps comes from refusing work, not faster code — budgets beat brilliance.

2

Fixed-step simulation keeps gameplay identical across hardware tiers.

3

The 38MB ceiling is why the game survives real life — calls, texts, background apps.

Article FAQ

Common Follow-Ups

The engine renders at display rate — on 60Hz panels you still get the simulation's full 240Hz input sampling.

Selected modules already are — the fixed-step scheduler and pooling allocator are on the studio's public repo.
Feel the Difference

Race the Flat Frameline

Launch the game, watch a replay at 1/8 speed — the smoothness you're seeing is bookkeeping.