inspect-limits

Overview ¶

Command inspect-limits reports whether a running container actually received the resource ceiling the benchmark intended (issue #141 §7 requires the suite to "detect and report that fact rather than silently pretending limits were applied"). It reads the limits Docker recorded for the container from `docker inspect` and classifies them against the intended budget via benchmarks/internal/reslimits, printing the honest verdict.

# after `docker compose ... up -d gin-gorm`:
go run ./benchmarks/scripts/inspect-limits \
  -container benchmarks-gin-gorm-1 -cpus 2 -memory 1g

This command prints the verdict; `make benchmark-crud-all` consumes it, passing the string to `run-crud -resource-limits` so a run records the applied limit (standalone, you can do the same by hand via `run-crud -resource-limits "$(inspect-limits …)"`). With -strict it exits non-zero unless the budget was fully enforced, so a caller that wants to refuse rather than record can fail closed.