bootgly/bootgly_benchmarks repository overview

⁠🏁 Bootgly — cross-framework benchmark (one command, zero setup)

bootgly/bootgly_benchmarks publishes the Bootgly PHP Framework⁠ HTTP_Server_CLI TechEmpower⁠ benchmark as self-contained images: each tag bundles Bootgly + one opponent runtime + PostgreSQL (which boots and seeds itself) and runs the whole benchmark from a single docker run — no install, no config, no database setup.

⁠🚀 Quick start

Sweep the server-worker count 1 → 24 for Bootgly vs Swoole on the TechEmpower routes, in a single run, and write the charts to ./results:

docker run --rm -v "$(pwd)/results:/bootgly/storage/tests/benchmarks" \
  bootgly/bootgly_benchmarks:swoole \
  test benchmark HTTP_Server_CLI --opponents=bootgly,swoole \
  --loads=techempower:* --server-workers=1..24 --results=charts

The only requirement is a running Docker daemon. --server-workers=1..24 runs one round per worker count in the same container; --results=charts writes per-round .bench.marks, a Markdown report and native SVG charts (throughput / ratio / latency) to the mounted ./results directory — so you get each framework's peak across the whole sweep, not a single point. Drop the -v mount and --results=charts for a plain printed result.

⁠🥊 Run another opponent

Replace the image tag and the --opponents name:

docker run --rm -v "$(pwd)/results:/bootgly/storage/tests/benchmarks" \
  bootgly/bootgly_benchmarks:<image> \
  test benchmark HTTP_Server_CLI --opponents=bootgly,<opponent> \
  --loads=techempower:* --server-workers=1..24 --results=charts

The <image> tag and the --opponents name are the same word:

⁠🔧 Common tweaks

• Faster sweep: a full 1..24 sweep is thorough but long — step it with --server-workers=1..24:4 (every 4th count), list points with --server-workers=1,4,8,16, or pin one count with --server-workers=15.
• Static only (skip the DB): --loads=techempower:1,2 (plaintext + JSON).
• Machine-readable: add --format=json to print only a single JSON document (all rounds, results and artifact paths).
• Tuning passes straight through: --connections=512 --duration=10.
• External DB instead of the bundled one: -e DB_HOST=… -e DB_PORT=… -e DB_NAME=… -e DB_USER=… -e DB_PASS=….

⁠🏗️ Build one yourself

Each tag is one build arg on top of the published framework image, and that base is required — there is no default, because bootgly/bootgly publishes no moving stable alias and a default would freeze on a pre-release the day a stable ships:

docker build -f Dockerfile \
  --build-arg BOOTGLY_FRAMEWORK_IMAGE=bootgly/bootgly:<version> \
  --build-arg WITH_SWOOLE=1 \
  -t bootgly_benchmarks:swoole .

Images are linux/amd64: FrankenPHP is pinned by an amd64 digest and RoadRunner and Bun ship amd64 binaries. That is a property of the opponents, not an oversight.

⁠🧭 The three Bootgly images

📊 Full harness, worker sweeps and result charts: https://github.com/bootgly/bootgly_benchmarks⁠ · 📚 Guide: https://docs.bootgly.com/guide/docker⁠ · MIT