perf-baseline-manager

Maintaining a single performance baseline per version involves storing one JSON file at a canonical path for each build. This prevents duplicate baselines and overwrites older metrics, ensuring auditable cross-version comparisons for regression monitoring.

Storing performance metrics JSON for cross-version comparison is best achieved by enforcing one file per version in a dedicated baselines directory. This consolidation ensures traceability and prevents conflicting metrics across builds.

Having multiple performance baselines for one version causes tracking issues by creating conflicting metrics and ambiguity. Enforcing a single JSON baseline per version prevents this by overwriting older baselines to maintain one source of truth.

Creating or updating a performance baseline for a new build version involves running the manager with current metrics. It saves the JSON baseline at the canonical version path, overwriting any existing baseline for that specific version.

The performance baseline manager captures environment details within the JSON baseline to ensure reproducibility. This metadata allows you to trace exactly how and where the performance metrics were generated across builds.