perf(linux): hybrid renderer causes 3-4x FPS drop and ~10 ms surface wait with vsync off #1081
Labels
No labels
Context: Bug
Context: Enhancements
Platform: Android
Platform: Linux
Platform: Web
Platform: Windows
Platform: iOS
Platform: macOS
Release
Target: CI
Target: CLI
Target: Dependency
Target: Engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital#1081
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
On Linux/KDE, the user reports:
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
surface_acq: ~10.49 mssurface_acquire: ~10.48 ms (the wait is insidecurrent_surface_texture())total: ~2.58 mssurface_acqPrimary 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
main, same scene, camera, resolution, refresh, and settings.surface_acquire,present,total, GPU aggregate, FPS, resolution, refresh, and present mode for each run.Acceptance criteria