Two awf items from this performance report: github/gh-aw#21703
Both the main Execute Copilot CLI step (20:09:16→20:09:26) and the threat detection step (20:10:14→20:10:25) each spend exactly 10s waiting for awf-api-proxy and awf-squid to stop — these containers aren't responding to SIGTERM and hitting Docker's 10-second default timeout before SIGKILL. Adding stop_grace_period: 1s (or passing --time 1 to docker stop) on those two containers would save ~10s × 2 = 20s.
Both sandbox executions (main agent + threat detection) each wait ~12s in compose up --wait watching health checks: 6s for api-proxy/squid, then another 6s for awf-agent. These are Docker Compose default intervals (30s check every second after a 30s start period, but empirically taking 6s each). Tuning the healthcheck in the compose spec to interval: 1s, start_period: 0s would collapse each 6s wait to ~1-2s. Total: (12−3) × 2 = ~18s, or ~14s accounting for the main step running inside the timed portion.
@Mossaka I think the first may have been fixed (but not deployed)?
How about the second?
Two awf items from this performance report: github/gh-aw#21703
@Mossaka I think the first may have been fixed (but not deployed)?
How about the second?