Skip to content

PR 0131 Vulkan remove uniform only pipeline key permutations

github-actions[bot] edited this page Sep 18, 2026 · 1 revision

PR #131 — Vulkan: remove uniform-only pipeline key permutations

State: Merged Reviewed head: 87d922561e77c81188744ade4eac86967f0d2789 Role: Supporting implementation/test history. The primary technical reference is Performance-Research-G09-Pipeline-Key-Minimization.

Why it mattered

Pipeline identity should exclude values proven runtime-uniform-only. Canonicalize consistently across lookup, fallback, background work, and publication.

Processing difference

flowchart LR
    A["Before: Uniform-owned values created redundant pipeline identities."] --> B["PR #131"]
    B --> C["After: Canonical keys clear or mask those fields while dirty and uniform updates remain."]
Loading

Durable lesson

Pipeline identity should exclude values proven runtime-uniform-only. Canonicalize consistently across lookup, fallback, background work, and publication.

Avoid repeating

  • Do not infer correctness or cost from labels such as clean, finish, same handle, or disabled.
  • Preserve the ownership, range, publication, retry, identity, or progress contract exposed by the PR.
  • Keep focused correctness evidence separate from broad throughput claims.
  • Re-run the relevant negative control when moving the mechanism to another renderer or subsystem.

Evidence pointer

Architecture

This page records what the PR taught us. Current design, source status, future experiments, and acceptance rules belong on the linked technical reference page.

Clone this wiki locally