perf(linux): hybrid renderer causes 3-4x FPS drop and ~10 ms surface wait with vsync off #1081

Closed
opened 2026-11-07 03:28:23 +00:00 by SakulFlee · 0 comments
Owner

Summary

On Linux/KDE, the user reports:

  • Vsync is disabled.
  • Changing present modes (Fifo, Mailbox, etc.) does not change the result.
  • Before the hybrid renderer, the same hardware/OS/settings ran about 3-4x faster.
  • The current 55-row capture runs at ~75 FPS with surface_acq ~10.5 ms.

The simple "vsync residual" explanation no longer fully fits, because there is no vsync and present-mode changes have no effect. This may be a real regression or a swapchain/compositor interaction.

Current numbers

  • FPS: ~74.8
  • surface_acq: ~10.49 ms
  • surface_acquire: ~10.48 ms (the wait is inside current_surface_texture())
  • total: ~2.58 ms
  • GPU aggregate: ~0.49 ms, but timestamp readback is stale (#1076)
  • Higher-FPS Linux capture: ~307 FPS at ~1.7 ms surface_acq

Primary hypothesis

The hybrid renderer may have increased the real GPU frame time to ~10 ms, but the GPU timestamps are stale (#1076), so the CSV shows only ~0.49 ms. If true, current_surface_texture() is waiting for a free swapchain image because the GPU is still busy. That explains why vsync and present-mode settings do not change the wait, and why pre-hybrid was 3-4x faster.

Alternative: KDE/Wayland/X11 compositor pacing, extra frames in flight, or a swapchain/present stall.

Investigation

  • A/B the pre-hybrid commit against current main, same scene, camera, resolution, refresh, and settings.
  • Fix timestamp readback first (#1076) and compare the real GPU cost.
  • Test vsync off with every present mode, fullscreen and windowed, X11 and Wayland, and a plain compositor or gamescope.
  • Record surface_acquire, present, total, GPU aggregate, FPS, resolution, refresh, and present mode for each run.
  • Capture metadata is missing from the CSV; improve it in #1078.

Acceptance criteria

  • The cause is classified as engine, swapchain, or compositor.
  • Pre-hybrid throughput is restored, or the platform limitation is documented with a working configuration.
## Summary On Linux/KDE, the user reports: - Vsync is disabled. - Changing present modes (Fifo, Mailbox, etc.) does not change the result. - Before the hybrid renderer, the same hardware/OS/settings ran about 3-4x faster. - The current 55-row capture runs at ~75 FPS with `surface_acq` ~10.5 ms. The simple "vsync residual" explanation no longer fully fits, because there is no vsync and present-mode changes have no effect. This may be a real regression or a swapchain/compositor interaction. ## Current numbers - FPS: ~74.8 - `surface_acq`: ~10.49 ms - `surface_acquire`: ~10.48 ms (the wait is inside `current_surface_texture()`) - `total`: ~2.58 ms - GPU aggregate: ~0.49 ms, but timestamp readback is stale (#1076) - Higher-FPS Linux capture: ~307 FPS at ~1.7 ms `surface_acq` ## Primary hypothesis The hybrid renderer may have increased the real GPU frame time to ~10 ms, but the GPU timestamps are stale (#1076), so the CSV shows only ~0.49 ms. If true, `current_surface_texture()` is waiting for a free swapchain image because the GPU is still busy. That explains why vsync and present-mode settings do not change the wait, and why pre-hybrid was 3-4x faster. Alternative: KDE/Wayland/X11 compositor pacing, extra frames in flight, or a swapchain/present stall. ## Investigation - A/B the pre-hybrid commit against current `main`, same scene, camera, resolution, refresh, and settings. - Fix timestamp readback first (#1076) and compare the real GPU cost. - Test vsync off with every present mode, fullscreen and windowed, X11 and Wayland, and a plain compositor or gamescope. - Record `surface_acquire`, `present`, `total`, GPU aggregate, FPS, resolution, refresh, and present mode for each run. - Capture metadata is missing from the CSV; improve it in #1078. ## Acceptance criteria - The cause is classified as engine, swapchain, or compositor. - Pre-hybrid throughput is restored, or the platform limitation is documented with a working configuration.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
SakulFlee/Orbital#1081
No description provided.