feat: add throughput column and trend to model rankings tab and CSV export

[impoiler]

Summary

Adds throughput (tokens/second) as a new metric to the model rankings table, enabling users to compare model output speed alongside existing metrics like latency, cost, and token usage.

Changes

• Added throughput field to ModelRankingEntry and throughput_trend to ModelRankingTrend types
• Added a sortable "Throughput" column to the model rankings table, displaying tokens/sec with a trend badge
• Included throughput and throughput trend columns in the CSV export output

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

Navigate to the workspace dashboard and open the Model Rankings tab. Verify:

1. A "Throughput" column appears and displays tokens/sec values with trend badges
2. Clicking the "Throughput" column header sorts the table correctly
3. Exporting the rankings as CSV includes "Throughput (tok/s)" and "Throughput Trend (%)" columns with correct values

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

Screenshots/Recordings

Add before/after screenshots of the model rankings table showing the new Throughput column.

Breaking changes

• Yes
• No

Related issues

#1992
#5160

Security considerations

None.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 62bfae09-84b7-4e00-b6d1-ef092d648d4d

📥 Commits

Reviewing files that changed from the base of the PR and between ced1727 and 863a517.

📒 Files selected for processing (3)

• ui/app/workspace/dashboard/components/modelRankingsTab.tsx
• ui/app/workspace/dashboard/utils/exportUtils.ts
• ui/lib/types/logs.ts

📝 Walkthrough

Walkthrough

Model rankings now include typed throughput data, a sortable and formatted dashboard table column, and throughput fields in CSV exports with prior-period trend handling.

Changes

Model Ranking Throughput

Layer / File(s)	Summary
Ranking data and CSV export ui/lib/types/logs.ts, ui/app/workspace/dashboard/utils/exportUtils.ts	Model ranking entries and trends include throughput, and CSV exports add throughput and throughput trend columns.
Ranking table throughput display ui/app/workspace/dashboard/components/modelRankingsTab.tsx	The rankings table adds a sortable Throughput column that formats values and displays throughput trends.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• maximhq/bifrost#5180: Introduces the throughput formatting helper used by the rankings table.
• maximhq/bifrost#5194: Adds backend throughput fields consumed by the UI and CSV changes.

Suggested reviewers: akshaydeo, tejasghatte, pratham-mishra04

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding throughput to model rankings and CSV export.
Description check	✅ Passed	The description covers the required sections with summary, changes, testing, screenshots, breaking changes, issues, security, and checklist.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 07-14-feat_per_model_throughput_in_dashboard_ui

---

_{Comment @coderabbitai help to get the list of available commands.}

[impoiler]

• feat: persist logs page-size preference in localStorage and exclude error_details from list query #5327
• fix: simplify ApiKeySelectorView visibility condition for enforceVirtualKeys #5313
• fix: extend chat↔responses pricing fallback to work bidirectionally #5276
• docs: update audit log archival to document windowed, manifest-based archival with tuning fields #5234
• feat: add archiveInterval, archiveGracePeriod, and archiveMaxObjectBytes audit log archival config options #5229
• fix: reject out-of-range tool_sync_interval minutes to prevent nanosecond unit confusion overflow #5255
• fix: send only disabled on toggle and convert tool_sync_interval units in cache #5254
• feat: add prompt_tokens and completion_tokens to search stats #5245
• feat: show prompt/completion token breakdown in logs stats card #5244
• feat: add throughput column and trend to model rankings tab and CSV export #5195 👈 (View in Graphite)
• feat: add throughput (tokens/sec) to model rankings and trend data #5194
• feat: add throughput (tokens/sec) histogram endpoints and dashboard metrics #5181
• feat: add throughput (tokens/sec) charts to overview and provider usage dashboard tabs #5180
• fix: replace fan-out attribution with single-owner additive rollup and "Unassigned" bucket for dimension rankings #5168
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
ui/app/workspace/dashboard/components/modelRankingsTab.tsx	Adds the throughput column, sorting option, formatted value, and trend badge to the model rankings table.
ui/app/workspace/dashboard/utils/exportUtils.ts	Adds throughput and throughput trend values to the model rankings CSV output.
ui/lib/types/logs.ts	Adds throughput fields to the model ranking response types.

_{Reviews (10): Last reviewed commit: "feat: per model throughput in dashboard ..." | Re-trigger Greptile}

[Pratham-Mishra04]

Merge activity

• Jul 17, 11:05 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 17, 11:23 AM UTC: Graphite rebased this pull request as part of a merge.
• Jul 17, 11:25 AM UTC: Graphite rebased this pull request as part of a merge.
• Jul 17, 11:25 AM UTC: @Pratham-Mishra04 merged this pull request with Graphite.

The base branch was changed.