Godot developers detail two renderer optimizations, from Polygon2D to D3D12 shaders
A Godot blog post walks through a profiler-led Polygon2D mesh fix and a per-thread heap change that shortens D3D12 shader loading.
The Godot Engine blog has published a progress report on how the team finds and fixes CPU-side rendering costs. It describes a loop of identifying the bottleneck, understanding it, trying solutions and measuring again, using an external sampling profiler.
The first case concerns animated Polygon2D nodes. A game developer saw performance fall off with about 20 animated characters, and profiling showed the mesh being freed and recreated every frame. The fix uploads new vertex data to the existing mesh where the vertex count is unchanged. The author reports that this roughly tripled performance for animated Polygon2Ds in the test scene.
The second case is the D3D12 shader pipeline, where transpiling SPIR-V to DXIL is the slowest step. Profiling showed threads waiting on the operating system for heap memory. Giving each thread its own heap removed the stalls and saved 11 seconds of load time in the TPS demo.
For game developers using Godot, the post is mainly background on how engine performance work is done. Anyone profiling their own project can take the same approach: measure first, change one thing and re-measure.
Sources
Verified Oct 24, 2026 (official source). godotgame-enginesperformanceindie-games