Skip to main content

Entry Points

FlashInfer-Bench provides two equivalent command-line entry points:
Use --help on any subcommand to inspect all available flags:

Run Benchmarks

Run benchmarks against a local FlashInfer-Trace dataset:
This is equivalent to:
Useful options:
Run only selected definitions or solutions:
Resume an interrupted run:
Use a YAML config file to set per-op-type or per-definition eval parameters:
Use the isolated runner instead of the default persistent runner:

Run The Benchmark Server

Start an HTTP benchmark server against a local trace dataset:
Use --devices to pin specific CUDA devices, or omit it to use all available CUDA devices. For endpoint details and request/response examples, see Benchmark Server API.

Inspect Results

Summarize pass/fail counts and author rankings by average speedup:
Show the best solution for each definition:
Merge multiple local datasets into one output directory:
Render a console-oriented visualization of results:

Notes

  • The CLI supports local datasets via --local.
  • Log verbosity is controlled with --log-level {DEBUG,INFO,WARNING,ERROR} on supported commands.
  • The flashinfer-bench console script and python -m flashinfer_bench share the same implementation and behavior.