Skip to content

feat(evaluation): add topology filter chips on Recipe Comparison - #11

Merged
aistackdev merged 1 commit into
masterfrom
feat/recipe-topology-filter
May 26, 2026
Merged

aistackdev merged 1 commit into
masterfrom
feat/recipe-topology-filter

Conversation

@aistackdev

Copy link
Copy Markdown

Summary

Adds a "Filter by topology" chip row to /evaluation, alongside the existing "Filter by knob" row:

```
Filter by knob: [All] [Spec decoding] [Batch size] [Baseline only]
Filter by topology: [All] [1× (TP=1)] [2× (TP=2)]
```

Lets the user isolate a single deployment shape without scanning the Topology column.

Chips are auto-derived from rows (one per distinct `r.topology` string), sorted by total GPU count ascending. The row renders only when there's more than one topology in the data (matches the knob-filter's auto-hide pattern).

Filter chain: topology AND (category | baseline). Baseline rows still show through any non-"all" category filter as a reference variant.

Test plan

  • `pnpm typecheck` clean
  • Post-deploy: with both 1×H100 (mnbt) and 2×H100 (MTP) data present, two chips render; selecting either narrows the table to that topology only.

🤖 Generated with Claude Code

Mirrors the existing 'Filter by knob' chip group with a 'Filter by
topology' row. Lets the user isolate a single deployment shape
(e.g. 1× (TP=1) vs 2× (TP=2)) and read the table without mixing rows
from different hardware layouts.

Chips are derived from rows: one per distinct r.topology string, sorted
by total GPU count ascending. Only renders when more than one topology
is present (matching the knob-filter chip's auto-hide pattern).

Filter chain in `rows`: topology AND (category | baseline). Baseline
rows still show through any non-"all" category filter to provide a
reference variant.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@aistackdev
aistackdev merged commit d4b11ae into master May 26, 2026
3 of 9 checks passed
@aistackdev
aistackdev deleted the feat/recipe-topology-filter branch May 26, 2026 09:55
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