> ## Documentation Index
> Fetch the complete documentation index at: https://codspeed.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> Learn how to ignore a benchmark from a report

# Ignoring a Benchmark

## Reasons to ignore a benchmark

**Ignoring a benchmark should be a last resort** when the source of flakiness
cannot be immediately addressed. Some reasons to ignore a benchmark include:

* The benchmark is I/O bound (network access, file-system access, etc.), leading
  to inconsistent results
* The benchmarked source code has a non-deterministic behavior (random number
  generation, memory allocation, etc.)
* The benchmark is consistently flaky for no apparent reason

Remember, the **goal of CodSpeed is to provide accurate and reliable
measurements**. Ignoring a benchmark should be a temporary measure until the
source of flakiness can be addressed.

<Tip>
  **Before ignoring a benchmark with expected variance**, consider using
  [per-benchmark regression
  thresholds](/features/customization/#per-benchmark-regression-thresholds)
  instead. This is ideal when the benchmark has predictable variability due to
  its nature (e.g., I/O operations with consistent but higher variance) rather
  than random flakiness. This approach lets you maintain performance tracking
  while accommodating the benchmark's inherent characteristics.
</Tip>

## Effects of ignoring a benchmark

An ignored benchmark will be **excluded from the overall measure** of a report.

However, it will still be accessible at the bottom of the report, in the
*Ignored* section. This allows you to keep track of ignored benchmarks, and keep
access to their [execution profiles and flamegraphs](/features/profiling) and
re-enable them once the source of flakiness has been addressed.

Ignoring or un-ignoring a benchmark **will regenerate and potentially modify the
reports of the latest commits of the default branch and branches with opened
pull requests**.

## How to ignore a benchmark

<Note>
  **Ignoring Permissions**: When working with an organization's repository, **only
  the admins** are allowed to ignore or un-ignore benchmarks.
</Note>

To ignore a benchmark, follow these steps:

1. Navigate to the benchmark's dashboard. You can do this by clicking on the
   button in the report or directly through the benchmarks page

2. Once on the benchmark's dashboard, click on the *Ignore* button

3. Enter a reason for ignoring the benchmark. This information will be used by
   CodSpeed to prioritize areas where we can reduce the flakiness of benchmarks.

4. Click on the *Ignore* button to confirm the action

## How to un-ignore a benchmark

You can reverse the effects of ignoring a benchmark by simply clicking on the
*Un-ignore* button on an ignored benchmark's page.