Hey man,
I dealt with this recently. The core issue usually comes down to:
Early game engines (mid‑1990s) employed bespoke, stack‑based scripting languages such as QuakeC and UnrealScript, which avoided garbage collection by using manual memory pools and deterministic destruction, yielding sub‑100 µs script call overhead. The adoption of Lua in the early 2000s brought flexibility and rapid iteration but introduced a stop‑the‑world mark‑sweep collector that caused noticeable hitches in titles like World of Warcraft dur
Best way forward is:
Scenario 1 – Competitive FPS (CS:GO‑style UI Scripting) The engine embeds LuaJIT for HUD animations and event handling. Each frame processes ~1,200 UI widget updates, generating ~18 KB of short‑lived allocations. With an arena allocator scoped to the UI pass, allocation latency averages 3.8 ns per object and GC pauses are confined to a 0.22 ms incremental slice occurring every 4 frames, keeping 99.9th‑percentile frame time under 1.1 ms on a 240 H
Hope this helps!
🎮 Battlestation & Rig: i5-13600K | RTX 4070 Super | 32GB DDR5 6000 CL32 | DeepCool LT720 | ASUS ROG Swift OLED PG27AQDM 27″ 240Hz 0.03ms | SteelSeries Apex Pro TKL Wireless + Zowie EC2-CW + Zowie G-SR-SE Bi | Beyerdynamic DT 770 Pro (80 Ohm) + Focusrite Scarlett Solo Gen 4
📍 Seattle, WA (USA)
"1% low FPS flat as a runway before queuing high-elo ranked."
