Do Godot’s Built‑In Profiler Capture GPU‑Bound Stalls?

Goal

Determine whether the Godot 4.x editor Profiler reports GPU‑bound stalls or only CPU‑side script execution times.

Constraints

• Script times appear near zero in the Profiler while the game’s FPS drops significantly.
• The Profiler samples frame time by category (process, physics, custom) and lists per‑function times for GDScript and engine calls.
• Performance monitors expose FPS, process and physics time, and render counters via Performance.get_monitor() or RenderingServer.get_rendering_info().
• External vendor GPU profiling tools are available but not yet integrated into the editor.

Unresolved Questions

1. Does the built‑in Profiler include GPU‑side time measurements for fragment shader execution, overdraw, or draw‑call latency?
2. If GPU time is not captured, which built‑in counters (e.g., RenderingServer.get_rendering_info() or Performance monitors) can reliably indicate GPU load?
3. When the Profiler shows clean script times but FPS remains low, should the developer rely on external vendor tools for GPU profiling, or can Godot’s internal counters suffice?