OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

Benchmark

Benchmark is a Go-based command-line framework for testing and comparing Ethereum execution clients. It runs configurable workloads, measures performance indicators such as latency and throughput, and presents results in an interactive dashboard.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Benchmark — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Benchmark when you need repeatable, configurable execution-client performance comparisons or want to examine workload behavior before deployment. Its payload simulator is useful when real-chain block characteristics should inform test workloads.

Who it is for

  • Developers comparing execution clients such as Geth and Reth.
  • Infrastructure teams investigating performance bottlenecks before deployment.
  • Teams tracking benchmark runs across workloads, configurations or machines.

Documented uses

  • Compare block-building and validation performance across execution clients.
  • Measure client behavior under configurable transaction patterns and workloads.
  • Review latency, throughput and submission-time metrics in reports.
  • Import and merge results from different machines or configurations.
  • Analyze real-chain block characteristics to inform benchmark configurations.
Before you choose

Requirements & limits

The project is an open-source repository licensed under MIT. Running it requires a local build; the dashboard requires Node.js 18 or later.

  • The documented CLI uses configurable benchmark files and accepts paths for Geth and Reth binaries.
  • Go 1.21 or later and Foundry are listed as prerequisites; Node.js 18 or later is needed for the dashboard.
  • The payload simulator requires an RPC endpoint supporting debug_executionWitness.
  • The README links public Devnet results; Base Sepolia and Base Mainnet results are marked as coming soon.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Build and run a documented benchmark

Build the Benchmark CLI and run the repository's basic public benchmark configuration.

Before you start

  • Go 1.21 or later
  • Foundry for smart-contract compilation
  • The repository and its submodules

Steps

  1. Clone the repository and initialize its submodules.

  2. Build the application with the command below.

    Documented command
    make build

  3. Run ./bin/base-bench run --config ./configs/public/basic.yml --root-dir ./data-dir --output-dir ./output.

Expected outcome

The documented command runs a benchmark using the basic public configuration and writes results to the specified output directory.

Guide limitations

  • The README does not specify machine-resource requirements or expected run duration.
  • Building Geth and Reth from source is optional; pre-built binary paths can be specified.
Documentation 1 ↗
Source-based practical guide

Open benchmark results in the local dashboard

Start the interactive dashboard for viewing benchmark results.

Before you start

  • Node.js 18 or later
  • The repository's report/ directory

Steps

  1. Change to the report/ directory.

  2. Run the command below.

    Documented command
    npm install

  3. Run the command below and open the browser URL shown in the terminal.

    Documented command
    npm run dev

Expected outcome

The local interactive dashboard opens for viewing benchmark results.

Guide limitations

  • The documented dashboard command starts a local development server.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
base/benchmark · Official homepage title · retained in its source language
How we review sourcesSuggest a correction