Full Benchmark Report

The Full Benchmark Report represents the complete output of benchmark execution.

It contains every successfully executed benchmark request together with all measured performance metrics, execution metadata, verification results, benchmark configuration, hardware information, and execution statistics.

Unlike the remaining report formats, the Full Benchmark Report intentionally preserves all benchmark execution details.

This report serves as the authoritative source from which every other benchmark report is generated.

For this reason, the Full Benchmark Report should always be preserved after benchmark execution.

Purpose

The Full Benchmark Report has several primary purposes.

• Preserve complete benchmark execution.
• Allow future score recalculation.
• Enable historical comparison.
• Support benchmark diagnostics.
• Provide reproducible benchmark data.

Unlike compact score reports, the Full Benchmark Report contains enough information to regenerate scoring results using future scoring versions.

Report Generation

The report is generated immediately after benchmark execution completes successfully.

Every executed benchmark request contributes one or more benchmark records.

Failed benchmark requests are also recorded together with failure diagnostics.

The report therefore represents the exact execution state of the benchmark.

Report Structure

The report consists of several logical sections.

General Information

Contains benchmark identifiers and execution metadata.

Hardware Snapshot

Describes the hardware configuration used during benchmark execution.

Benchmark Configuration

Contains benchmark parameters supplied during execution.

Category Results

Contains raw execution results for every benchmark category.

Execution Statistics

Contains execution counters and timing information.

Failures

Contains benchmark failures together with diagnostic information.

Together these sections completely describe one benchmark execution.

General Information

The report begins with general benchmark metadata.

Typical information includes:

• Report identifier
• User identifier
• Benchmark version
• Scoring version
• Execution timestamp
• Operating system
• Architecture
• Benchmark duration

These values uniquely identify the benchmark execution.

Hardware Snapshot

The complete detected hardware configuration is embedded directly inside the report.

The hardware snapshot contains:

Processor

• Processor model
• Physical cores
• Logical processors

Memory

• Installed capacity
• Available memory
• Memory modules
• Manufacturer
• Frequency
• ECC information

Storage

• Storage devices
• Firmware versions
• Benchmark storage device

Operating System

• Operating system
• Architecture
• Hostname

Hardware Fingerprint

• Deterministic hardware identifier

Embedding the hardware snapshot directly into the report guarantees long-term reproducibility.

Benchmark Configuration

The report records every benchmark parameter used during execution.

Examples include:

• Executed benchmark categories
• Worker configurations
• Benchmark directory
• Report identifier
• User identifier
• Measured iterations
• Warmup iterations
• Compilation environment

Recording benchmark configuration allows historical benchmark executions to be reproduced exactly.

Benchmark Results

The largest section of the report contains raw benchmark execution results.

Every benchmark category records its own execution format.

Examples include:

JSON

• Throughput
• Object counts
• Dataset sizes

Hashing

• Processed bytes
• Algorithm
• Throughput

Encryption

• Processed bytes
• Algorithm
• Verification

Compilation

• Build duration
• Compiler
• Build profile
• Build verification

Storage

• Throughput
• Operations
• Block sizes
• Filesystem configuration

Raw benchmark results remain intentionally category-specific.

No normalization is performed inside the Full Benchmark Report.

Verification Results

Every benchmark execution records verification status.

Verification includes:

• Execution success
• Validation status
• Verification failures
• Diagnostic messages

Only verified benchmark executions participate in score generation.

Failures remain preserved for diagnostic purposes.

Execution Statistics

Execution statistics summarize benchmark progress.

Typical statistics include:

• Planned requests
• Executed requests
• Successful requests
• Failed requests
• Planned scenarios
• Successful scenarios
• Failed scenarios
• Total benchmark duration

These values provide a quick overview of benchmark execution quality.

Timing Information

Execution timing is recorded both globally and per benchmark category.

Examples include:

• Total execution duration
• JSON benchmark duration
• Hashing duration
• Encryption duration
• Compilation duration
• Storage duration

Recording execution timing allows benchmark users to identify which benchmark categories dominate overall execution time.

Failure Information

If benchmark execution encounters failures, diagnostic information is preserved.

Typical failure information includes:

• Benchmark category
• Scenario
• Request parameters
• Failure reason
• Verification status
• Execution directory

Failures never prevent successful benchmark results from being preserved.

Instead, they become part of the benchmark history for later investigation.

Relationship to Other Reports

The Full Benchmark Report acts as the source for every remaining benchmark report.

            Full Benchmark Report
                     │
                     ├────────► Scoring Report
                     │
                     ├────────► Global Score Report
                     │
                     └────────► Benchmark Comparison

No additional benchmark execution is required to generate these reports.

Every subsequent report is derived exclusively from the Full Benchmark Report.

Long-Term Compatibility

The Full Benchmark Report has been designed for long-term compatibility.

Future benchmark releases may introduce:

• Additional benchmark categories
• Additional workload parameters
• New scoring versions
• New diagnostics

Historical reports remain valid because benchmark execution data is preserved independently from score calculation.

This design allows benchmark scores to be recalculated in the future without repeating benchmark execution.

Design Summary

The Full Benchmark Report represents the complete historical record of one benchmark execution.

It preserves benchmark configuration, hardware information, execution results, diagnostics, verification status, timing information, and execution statistics in a deterministic and versioned format.

Because every remaining benchmark report is derived from this document, the Full Benchmark Report serves as the authoritative source of benchmark information and should always be preserved for future analysis, comparison, and score recalculation.