ethpandaops/Benchmarkoor

Run Ethereum execution client benchmarks using benchmarkoor

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Jul 10, 2026
License: GPL 3.0

Pinned Snippet

workflow.ymlSHA-pinned

uses: ethpandaops/benchmarkoor@e366d0618ae339b01e7d266860844d6c133bbbc0 # v0.1.0

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
github-token	GitHub token for API access	yes	—
mode	Which phase(s) to run: "all" (build if a build-config is set, then run — the default), "build" (build only, no run), or "run" (run only, skip build even if a build-config is set).	no	all
image	Docker image to extract the benchmarkoor binary from (e.g., ghcr.io/ethpandaops/benchmarkoor:master). If not provided, will build the image locally from git-ref/git-repo and extract from it.	no	""
git-ref	Git branch or commit hash to build from. Only used when image is not provided. Defaults to master.	no	""
git-repo	Git repository URL to clone for building the image. Only used when image is not provided. Defaults to ethpandaops/benchmarkoor.	no	https://github.com/ethpandaops/benchmarkoor.git
upload-artifacts	Whether to upload run results as GitHub artifacts	no	false
upload-build-artifacts	Whether to upload build artifacts as a GitHub artifact: each state-actor target's metadata JSON (not the datadir) and each eest-payloads target's full fixtures directory.	no	false
build-artifact-name	Name for the uploaded build artifact. Override to disambiguate matrix legs (artifact names must be unique within a run), e.g. append the client. Leave empty for the default `benchmarkoor-build-<run_id>`. Only used when upload-build-artifacts is true.	no	""
run-config-urls	Comma-separated URLs for config files to download and pass via --config (merged in order)	no	""
run-config	Raw YAML config content to pass via --config (appended after URL config)	no	""
run-args	Extra flags passed to benchmarkoor run command	no	""
build-config-urls	Comma-separated URLs for config files to download and pass to `benchmarkoor build` via --config (merged in order). Setting this or build-config enables the build phase (state-actor snapshots + eest payloads), which runs before the benchmark run.	no	""
build-config	Raw YAML config content to pass to `benchmarkoor build` via --config (appended after URL config). Setting this or build-config-urls enables the build phase.	no	""
build-args	Extra flags passed to the benchmarkoor build command (e.g. --force, --limit-state-actor-target=)	no	""
tmp-dir	Temporary directory path used for benchmarkoor data (overlayfs) and cache	no	/tmp

Outputs

no outputs