Skip to content

QVAC-20614 docs: platform & GPU-backend benchmark coverage matrix#45

Open
Zbig9000 wants to merge 1 commit into
tetherto:masterfrom
Zbig9000:QVAC-20614-gpu-coverage-matrix
Open

QVAC-20614 docs: platform & GPU-backend benchmark coverage matrix#45
Zbig9000 wants to merge 1 commit into
tetherto:masterfrom
Zbig9000:QVAC-20614-gpu-coverage-matrix

Conversation

@Zbig9000

Copy link
Copy Markdown

What

Adds a platform × GPU-backend coverage matrix to the speech-stack READMEs —
for each engine, which backends build and where we have current CI benchmark
numbers
vs maintainer-measured / pending / GPU-disabled.

  • README.md — consolidated speech-stack matrix covering whisper, parakeet,
    Chatterbox, Supertonic
    × CPU / Vulkan / Metal / CUDA / Android, with a legend
  • parakeet-cpp/README.md — per-platform backend coverage table (sits above
    the CI benchmark numbers).
  • tts-cpp/README.md — Chatterbox + Supertonic per-platform coverage table.

Why

Follow-up to the QVAC-20614 benchmark refresh: makes the GPU/platform support +
benchmark coverage explicit and surfaces the known gaps in one place.

Known gaps captured

Test plan

  • READMEs render (tables + anchor links resolve)

Document, per engine, which backends build and where we have current CI
benchmark numbers vs maintainer-measured / pending / GPU-disabled:
- README.md: consolidated speech-stack matrix (whisper, parakeet, Chatterbox,
  Supertonic) x CPU/Vulkan/Metal/CUDA/Android, with whisper GPU marked pending.
- parakeet-cpp/README.md: per-platform backend coverage table.
- tts-cpp/README.md: Chatterbox + Supertonic per-platform coverage table.

Captures the known gaps: Supertonic GPU re-land (qvac#2506), Android Adreno
force-CPU (qvac#2525/ggml-org#2506), CUDA not yet benchmarked, iOS Metal pending.
@Zbig9000 Zbig9000 requested review from a team as code owners June 12, 2026 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant