How we check the work

# Results you   can examine.

Every featured result names the work produced and the checks behind it.

On this page [Start with the work produced ](#section-0) [Check behavior before comparing performance ](#section-1) [Keep the result connected to its setup ](#section-2) [Read the result in detail ](#section-3) [Read as Markdown ](/benchmarks/methodology/index.md) 

## Start with the work produced

An example begins with a problem and what came back: a code patch, a faster implementation or a changed circuit. We name the project and describe how the output was used.

## Check behavior before comparing performance

For the Java migration, we replayed the build and original tests. For compression, we checked decoding and output sizes. For the circuit, formal equivalence checks tested the supported configurations.

## Keep the result connected to its setup

Each case includes the relevant versions, workload and measurement conditions. Detailed result records identify the selected artifact and the scope of the comparison.

## Read the result in detail

Open an example for the outcome, then expand its method for the checks and comparison.
[Explore fleet results ](/examples/) 

[Fleet results ](/examples/)