feat(experiments): parameterize TIME_SCALE in E4-pressured sweep

The third_party SWE-Bench trace uses real wall-clock timestamps
(5.44h span, p50 inter-turn 2.53s). With --time-scale 1 the sweep
mirrors the original timeline, taking 5.44h. TIME_SCALE env var
lets us compress (e.g. 10 → 33min, 60 → 5.5min) for tighter
iteration; defaults to 1 for realistic comparison.

Usage:
  TIME_SCALE=10 bash scripts/sweep_e4_pressured.sh
  TIME_SCALE=60 bash scripts/sweep_e4_pressured.sh
This commit is contained in:
Claude Code Agent
2026-05-13 14:22:13 +08:00
parent a953346a0c
commit 19612ff3a3

View File

@@ -32,6 +32,9 @@ IB_DEVICE=${IB_DEVICE:-mlx5_60}
LOAD_FLOOR_BONUS=${LOAD_FLOOR_BONUS:-200}
REJECT_THRESHOLD=${REJECT_THRESHOLD:-1}
MEM_FRACTION=${MEM_FRACTION:-0.5}
# time-scale: 1 = realistic 5.44h timeline for the SWE-Bench trace;
# 10 = compress to ~33 min; 60 = compress to ~5.5 min (stress test).
TIME_SCALE=${TIME_SCALE:-1}
if [ ! -f "$TRACE" ]; then
echo "ERROR: trace not found at $TRACE" >&2
@@ -63,7 +66,7 @@ uv run --no-sync python -m agentic_pd_hybrid.cli benchmark-live \
--transfer-backend mooncake \
--force-rdma --ib-device "$IB_DEVICE" \
--gpu-budget 4 \
--time-scale 1 \
--time-scale "$TIME_SCALE" \
--session-sample-rate 1.0 \
--target-duration-s 100000 \
--concurrency-limit 32 \