feat: ingest and display kv_transfer_lib on benchmark results

[Oseltamivir]

Summary

The benchmarking repo is gaining runtime detection of the KV-cache transfer library (Mooncake, NIXL, MoRI-IO, UCX) for disaggregated runs, emitted as an optional kv_transfer_lib string on result rows (companion InferenceX PR, branch feat/kv-transfer-lib-metadata). This PR is the forward-only app side: ingest the field when present and show it in chart tooltips. Until now the transfer library was invisible downstream — dynamo-sglang covers both Mooncake (DSV4 recipes) and NIXL (GLM-5 STP recipes) under one framework key; only mooncake-atom / mori-sglang encoded it in the name.

Changes

DB (packages/db)

• Migration 008: nullable kv_transfer_lib text column on benchmark_results (+ lowercase CHECK). Result-level metadata, deliberately not part of the config natural key — config identity and trend-line continuity are unchanged. Recreates the latest_benchmarks materialized view (it materializes select br.* at creation time) with the identical migration-007 definition.
• benchmark-mapper: surfaces the field as a metrics sibling (like workers), trimmed/lowercased, defensively narrowed — absent/empty/non-string ⇒ undefined.
• benchmark-ingest: writes the column (NULL when absent), included in the conflict-update path.
• All four benchmark SELECTs and the json-provider return it.

App (packages/app)

• BenchmarkRow → AggDataEntry → InferenceData passthrough.
• Tooltips show a KV Transfer line (Mooncake / NIXL / MoRI-IO / UCX; unmapped values uppercased) in the parallelism/configuration section of all three tooltip variants: official, unofficial-run overlay, and GPU date-comparison. NULL/absent renders nothing — unknown is never guessed to a default.
• unofficial-run route carries the field from raw artifacts so overlays match the official path.

Unofficial run overlay support

Works for both official runs and ?unofficialrun= overlays: the overlay path reuses mapBenchmarkRow + transformBenchmarkRows, and the route copies kvTransferLib into the overlay BenchmarkRows. Covered by unit tests on the overlay route (route.test.ts) and the overlay tooltip generator (tooltip-utils.test.ts). Note: live manual verification isn't possible yet — no artifacts contain the field until the benchmarking-repo PR merges and a run lands; the overlay tests pin the behavior in the meantime.

Existing data

Historical rows stay NULL and the tooltip simply omits the line. If backfill is ever wanted, AMD history is derivable from the framework column alone (mooncake-atom ⇒ mooncake, mori-sglang ⇒ mori, vllm-disagg ⇒ nixl) in one UPDATE; recipe-driven dynamo-* history would need a git-history walk and is intentionally out of scope.

Testing

• pnpm typecheck, pnpm lint, pnpm fmt clean.
• New unit tests: mapper capture/normalization/narrowing (db), transform passthrough, tooltip line in all three variants incl. absent-field omission, overlay route carry/null. All touched files pass; the 13 pre-existing use-feature-gate / chunk-load-recovery / visit-tracker failures reproduce on clean master and are unrelated.

Sequencing

• Reads are migration-tolerant: all four benchmark read queries surface the column via to_jsonb(row) ->> 'kv_transfer_lib' (the migration-006 workers rollout pattern), so previews and prod work whether or not migration 008 has run. A regression test pins this.
• Migration 008 must run before the first ingest of field-bearing artifacts — the ingest INSERT references the column directly. Since artifacts only carry the field once the benchmarking-repo PR merges, running the migration any time before that is sufficient.

---

Note

Medium Risk
Touches benchmark ingest and all benchmark read queries plus a materialized view rebuild; mis-sequenced migration could 500 the dashboard, though the to_jsonb guard and optional field limit blast radius.

Overview
Adds optional KV-cache transfer library metadata (mooncake, nixl, mori, ucx) for disaggregated benchmark runs, from runner artifacts through the DB to chart tooltips—without changing config identity or trend lines.

Database: Migration 008 adds nullable kv_transfer_lib on benchmark_results (lowercase CHECK), rebuilds latest_benchmarks, and the ingest path maps, normalizes, and upserts the field separately from scalar metrics (same pattern as workers).

API reads: Benchmark SELECTs expose the value via to_jsonb(row) ->> 'kv_transfer_lib' so queries still plan when migration 008 is not applied yet.

App: The field flows BenchmarkRow → chart points → KV Transfer in official, unofficial overlay, and GPU date-comparison tooltips (known labels mapped; absent/null omits the line). The unofficial-run overlay route passes it through from artifacts.

^{Reviewed by Cursor Bugbot for commit 22a039c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
inferencemax-app	Ready	Preview, Comment	Jul 3, 2026 3:21am