Drop 'capped' from per-policy figures (f4a, f4c×2, f6)
'capped' is not a routing policy — it's lmetric run on a separately truncated trace (sessions capped to 8 turns via build_capped_trace.py). Putting it alongside lmetric/load_only/sticky/unified in per-policy comparison figures is misleading because the workload differs, not the routing decision. Comparing apples to a different-trace orange inflates/deflates apparent policy gaps for the wrong reasons. Regenerated 4 figures with --exclude-policies capped on analysis/characterization/render_window1_figures.py: - f4a_apc_loss.png (APC bars) - f4c_apc_vs_hotspot_tradeoff.png (APC vs hotspot scatter) - f4c_per_worker_ttft.png (per-worker TTFT panel) - f6_e2e_latency_bars.png (TTFT/TPOT/E2E bars) Added --exclude-policies CLI flag to the renderer so this is a reversible choice, not a permanent script mutation. capped data remains in b3_policy_comparison.json and can be brought back in workload- sensitivity sections (where it actually belongs) by omitting the flag. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Before Width: | Height: | Size: 38 KiB After Width: | Height: | Size: 35 KiB |
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 45 KiB |
|
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 54 KiB |