cost_analysis: region / fleet / per-PR-commit / category breakdowns

[wdvr]

What

New breakdowns on /cost_analysis: region, fleet (OSDC/ciforge vs regular EC2), cost per PR / commit / main commit, cost by category (inside-PR / after-merge / nightly / periodic / benchmark / other), merge rate and slop, CI volume, and a top-down CI-vs-overhead view.

UI (pages/cost_analysis.tsx)

• Region and Fleet added as group-by dimensions.
• Cost per unit (PR / plain commit / main commit) + a CI volume / merge / slop / category-$ table.
• Per-PR-by-fleet and by-category over time, each with $ / hours / % and line / stacked toggles (icons match the top chart).
• Top-down panel: attributed CI vs overhead/idle (account-wide).
• Tables pin the first column.

Queries (clickhouse_queries/*)

• Region and fleet are inferred from the runner type (no runner_cost column needed); region is approximate.
• Per-PR/commit/category/slop read misc.unit_cost_daily / misc.unit_keys; the overhead panel reads misc.infra_overhead_daily.

Depends on

• meta-pytorch/pytorch-gha-infra#1189 (prices mt-* runners via Vantage; builds unit_cost_daily / unit_keys)
• meta-pytorch/pytorch-gha-infra#1192 (builds infra_overhead_daily)

Draft until those land in prod. Verified locally against a dev ClickHouse.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
torchci	Ready	Preview	Jun 2, 2026 11:41pm

[meta-cla]

Hi @wdvr!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!