Archive benchmarks when the benchmarked code has been permanently removed from your codebase or when benchmarks are no longer relevant to your project.Archive benchmarks when:
The benchmarked code has been deleted or deprecated
Benchmarks are consistently skipped due to removed functionality
You want to clean up obsolete benchmarks from active reports
Benchmarks are temporarily disabled but may be re-enabled
You’re unsure if the benchmark will be needed in the future
Unlike ignoring benchmarks, archival is for removed code. Archived benchmarks can be restored at any time, but they are completely removed from active reports.
An archived benchmark will be completely removed from active reports. However, all historical data is preserved and the benchmark can be restored at any time.Archived benchmarks can be found in the Archived tab on the benchmarks page, and their individual dashboard pages remain accessible with full historical data.Archiving or restoring a benchmark will regenerate and potentially modify the reports of the latest commits of the default branch and branches with opened pull requests.