Command Line Interface

The Scalionix System Benchmark is executed entirely through its command-line interface.

The CLI has been designed with several primary objectives.

• Simple execution.
• Predictable behavior.
• Deterministic benchmark configuration.
• Complete automation.
• Easy integration with CI/CD systems.

Every benchmark execution is fully controlled through command-line flags.

No interactive input is required.

This design allows the benchmark to be executed manually, integrated into automated performance testing pipelines, or incorporated into continuous integration environments.

Basic Execution

Executing the complete benchmark requires only a single command.

scalionix-system-benchmark

The benchmark automatically performs the following steps.

• Detect hardware.
• Verify benchmark environment.
• Create benchmark workspace.
• Execute benchmark categories.
• Calculate normalized scores.
• Generate benchmark reports.
• Print execution summary.

When no additional flags are supplied, the benchmark executes using its default configuration.

Execution Pipeline

Every benchmark execution follows the same deterministic workflow.

Command Line
      │
      ▼
Parse Arguments
      │
      ▼
Validate Configuration
      │
      ▼
Detect Hardware
      │
      ▼
Prepare Benchmark
      │
      ▼
Execute Categories
      │
      ▼
Score Calculation
      │
      ▼
Generate Reports
      │
      ▼
Print Summary

Each stage is executed exactly once.

Any fatal error immediately terminates execution with a descriptive diagnostic message.

Command-Line Philosophy

Every command-line flag modifies only one aspect of benchmark execution.

Flags are intentionally independent whenever possible.

This design provides several advantages.

• Predictable execution.
• Simple automation.
• Easy scripting.
• Deterministic behavior.

Benchmark execution never depends on hidden configuration files.

Everything affecting benchmark execution is explicitly visible through the command line.

Output Files

Successful benchmark execution generates multiple output files.

Typical outputs include:

• Full Benchmark Report
• Scoring Report
• Global Score Report

Depending on execution mode, additional reports may also be generated.

The benchmark prints the location of every generated report after execution completes.

Exit Status

The benchmark returns standard operating system exit codes.

Exit code 0

Benchmark completed successfully.

Non-zero exit codes

Benchmark execution failed.

Typical failure reasons include:

• Invalid command-line arguments
• Missing benchmark environment
• Benchmark verification failures
• Filesystem errors
• Unsupported operating system configuration

This behavior allows the benchmark to integrate naturally with shell scripts and automated build systems.

Logging

Benchmark execution continuously reports progress to standard output.

Progress messages include:

• Benchmark category
• Executed scenario
• Worker configuration
• Execution progress
• Benchmark summary

Errors are reported immediately together with sufficient diagnostic information to identify the underlying problem.

Deterministic Execution

Given identical hardware, identical benchmark configuration, and identical benchmark version, the command-line interface always produces identical execution behavior.

No benchmark configuration is inferred implicitly.

Every execution parameter is either supplied explicitly or generated deterministically by the benchmark.

Design Summary

The Scalionix command-line interface provides a deterministic and automation-friendly interface for benchmark execution.

By exposing every important benchmark parameter through explicit command-line flags while avoiding hidden configuration, the CLI remains predictable, reproducible, and suitable for both interactive use and fully automated benchmark environments.