Repository navigation
Performance
xemu performance work should connect a measured symptom to a specific processing path, then prove that a proposed change improves that path without moving cost elsewhere or weakening correctness.
- Separate layers. Shader binding, stage-module compilation, graphics-pipeline creation, command-buffer submission, GPU execution, and guest-visible cadence are different measurements.
- Measure tails. Average FPS can stay flat while p95/p99 or single-frame stalls get worse.
- Keep source identity. A result belongs to the exact executable/source state that produced it.
- Retain adverse data. A workload-specific win does not erase a regression elsewhere.
- Distinguish diagnostics from product runs. Instrumentation can change timing.
- Preserve correctness oracles. A faster path is not an optimization if ordering, output, or guest-visible behavior changes incorrectly.
See Vulkan Performance for the current Vulkan documentation set.
The three initial pages deliberately cover different cost classes:
- Shader Binding & Compilation — CPU-side cache lookup, code generation, glslang, module creation, reflection, and graphics-pipeline preparation.
- Ubershader & Hybrid Specialization — changing a first-seen specialized shader from a synchronous draw dependency into a fallback-plus-background specialization flow.
- Vertex Uploads & Render-Pass Lifetime — memory coherency and command-buffer lifetime proof for avoiding ordered staged copies where safe.
Where a page reports an "Improvement %", verify the metric direction. Lower frame interval or CPU/GPU duration is good; higher guest progress/cadence can be good. Do not interpret a large percentage of time in a region as equally large removable overhead: the region may include useful work.
DSP tooling guide and navigation updated November 2, 2026 for experimental PR #384, source 8f51d237. Capture/replay usage and limits.
The earlier wiki-wide review was published November 1, 2026. Emulator source: b7140848. Reviewed wiki content: 1d2b671. Current status · Release availability · Publication process.
- Home
- Current status
- Stable versus main
- Implemented mechanisms
- Controls and defaults
- Measured results and limits
- Complete change register
- System
- CPU and vCPU
- Memory and DMA
- Graphics / NV2A
- APU and audio
- Timing and timers
- Platform and I/O
- Hardware observations
- Fidelity boundaries
- Methodology
- PGR2 routes
- Debugging lag / hot paths
- Tools and commands
- DSP capture, replay and fuzzing
- HLE readiness and public XISO proof
- Concurrent DSP shadow and OpenAL proof
- DSP HLE operation inventory
- DSP HLE fix examples and testing
- Development
- Upstream shortlist
- Wiki maintenance
- Research / retired work
- Optimization catalog
- Hot-path shortcuts
- Researched experiments
- Unproven proposal directory
- PR lessons
- September26 snapshot
Repository · PRs · Issues