Skip to content

Vulkan Performance

github-actions[bot] edited this page Sep 13, 2026 · 4 revisions

Vulkan Performance

This section documents Vulkan renderer performance by code path and ownership boundary.

Processing map

flowchart LR
    A[Guest/NV2A state] --> B[Shader state + binding]
    B --> C[Stage modules]
    C --> D[Graphics pipeline]
    D --> E[Draw recording]
    E --> F[Vertex/data synchronization]
    F --> G[Command buffer / render pass]
    G --> H[GPU execution]
Loading

A slowdown can appear at any of these layers. Similar symptoms do not imply the same cause.

Current detailed topics

Shader Binding & Compilation

Vulkan Shader Binding & Compilation explains how shader state becomes generated GLSL, SPIR-V, VkShaderModule objects, reflection state, shader bindings, and ultimately a graphics pipeline. It also documents why shader-binding misses, stage-module misses, and pipeline misses must be counted separately.

Ubershader & Hybrid Specialization

Vulkan Ubershader & Hybrid Specialization documents the fallback/interpreter route used to avoid making every admitted first-seen fragment specialization a synchronous draw dependency. It covers the control ABI, fail-closed admission, route policy, background compiler, required compiler lane, publication boundary, and descriptor-layout consequences.

Vertex Uploads & Render-Pass Lifetime

Vulkan Vertex Uploads & Render-Pass Lifetime documents the Vulkan-side mirror of guest vertex RAM and the proof required before replacing an ordered staged upload with a mapped CPU write during an active batch.

Relationship between the investigations

flowchart TD
    A[Measured bad frame] --> B[Classify shader/pipeline cost]
    B --> C[PR #68 diagnostic evidence]
    C --> D{First-seen specialization still blocks draw?}
    D -->|Yes| E[Fallback ubershader + background specialization]
    E --> F[PR #71]
    B --> G[Inspect other synchronization / pass disruption]
    G --> H[Vertex mirror lifetime proof]
    H --> I[PR #87]
Loading

PRs are implementation history and research references. The architecture pages are the durable source of explanation.

Clone this wiki locally