Define runtime budgets, measure repeatable scenarios, and fail CI on frame-time, memory, allocation, rendering, or physics regressions.Verified working in Unity 2022 and Unity 6.Performance goals only protect a release when they are written down, measured the same way, and allowed to fail the pipeline. Runtime Performance Budget CI turns repeatable game scenarios into explicit runtime budgets and evidence your CI can act on.What it helps you doDefine scenario suites with warmup, measurement, filtering, and repeat rules.Measure frame time, main-thread time, GC allocation, managed and total memory, renderer counters, and physics counters when the environment exposes them.Set absolute limits and baseline-regression limits per metric.Report unavailable counters as not measured instead of silently passing them.Fingerprint the environment and refuse to call unlike machines a regression.Measure in Editor play mode or a development player.Export deterministic JSON, Markdown, and self-contained HTML reports and return CI exit codes.Use it to protect a target frame budget, stop memory or allocation creep, or keep performance acceptance criteria beside the code that depends on them.This is a budget runner, not a profiler. It tells you which scenario and metric failed; use Unity Profiler to locate the code responsible. Batch mode does not render, so renderer counters require a supported Editor or development-player measurement.Read the complete documentation.PRODUCT TYPERuntime scenario measurement, budget evaluation, baseline comparison, reporting, and CI gate.REQUIREMENTSUnity 2022.3 or newer.No package dependency, account, service, or network access.A development player is required for player-side profiler counters.KEY FEATURESScenario and suite assets with warmup, sample count, filters, and deterministic identity.Frame time, main thread, GC allocation, managed heap, total/system memory, renderer, and physics metrics when exposed by the run mode.Absolute limits, tolerances, scopes, and baseline-regression rules.Explicit Not Measured status with a reason for unavailable counters.Environment fingerprints prevent cross-machine comparisons from being labelled regressions.Editor play-mode and development-player measurement paths.JSON, Markdown, and self-contained HTML reports with manifests and batch exit codes.IMPORTANT LIMITSNot a profiler and does not identify the method or shader responsible for a failed budget.Renderer counters are unavailable in headless batch mode because nothing is rendered.Editor play mode includes Editor overhead; player measurement is preferred for release gates.No GPU timings, automatic budget proposals, or automatic optimization.Full documentation.AI-assisted image generation was used for the package icon artwork, and AI-assisted drafting was used for marketing copy and documentation formatting. All technical claims were sourced from the package, and the code, functionality, layouts, exports, and final text were manually reviewed and verified.
