System Requirements Benchmarking

Use the portal benchmark command to generate measured requirement snapshots for the public /requirements page.

Command

Run from webapp/:

php artisan gnosis:benchmark-requirements \
  --base-url="http://127.0.0.1:9004" \
  --server-url="http://127.0.0.1:9005" \
  --requests=2400 \
  --concurrency=40

Optional output path:

php artisan gnosis:benchmark-requirements --path="/tmp/gnosis-system-requirements.json"

Portal-only benchmark (skip direct server probes):

php artisan gnosis:benchmark-requirements --no-server

Include direct server audience benchmark explicitly:

php artisan gnosis:benchmark-requirements --server-audience

What it measures

• portal health endpoint throughput
• portal audience feed endpoint throughput
• server health/public-site/audience-feed endpoint throughput (when --server-url is set)
• benchmark host CPU and memory metadata

Output

By default, snapshot JSON is written to:

storage/app/system_requirements_snapshot.json

Override with:

• --path=...
• or env GNOSIS_REQUIREMENTS_SNAPSHOT_PATH

Notes

• Requires ApacheBench (ab) in the execution environment.
• Re-run on production-equivalent hardware whenever host size, polling interval, or traffic profile changes.
• The command derives self-hosted profile targets from measured audience throughput with conservative safety factors.