5 Commits

Author	SHA1	Message	Date
yy-fighting	ee954d7409	fix(sglang-vs-vllm): use jq for metadata update; add results run 20260708-083346	2026-07-08 09:21:49 +00:00
yy-fighting	5eb605b7a2	feat: support resuming interrupted SGLang vs vLLM runs ... - run_bench.sh: skip scenarios whose raw jsonl already exists and has expected completed count - parse_backend.py: replace scenarios list instead of appending, so resume+reparse stays clean - README.md: document RUN_ID-based resume	2026-07-08 08:42:21 +00:00
yy-fighting	162168da3c	feat: record exact server launch args in results.json for reproducibility ... - sglang_vs_vllm/run_bench.sh: add phase1/phase2 server_args per backend - dspark_vs_default/run_bench.sh: add server_args for dspark/default - READMEs document where to find the recorded server args	2026-07-08 08:21:55 +00:00
yy-fighting	06b3398ad0	feat: add ShareGPT dataset scenarios to SGLang vs vLLM comparison ... - config.env: add SHAREGPT_DATASET, SHAREGPT_CONTEXT_LEN and SHAREGPT_SCENARIOS - run_bench.sh: add run_sharegpt() and integrate it after Phase 1 for each backend - parse_backend.py: support both phase{1|2} and sharegpt raw output filenames - README.md: document ShareGPT scenarios	2026-07-08 07:42:05 +00:00
yy-fighting	e6d9e99b6f	feat: add SGLang vs vLLM controlled comparison experiment ... - New experiments/dsv4_h200_sglang_vs_vllm/ with TP=8 on all 8 H200 cards - Phase1 short-context throughput + Phase2 long context up to 200k - Unified scenario matrix, warmup, parsing, and side-by-side comparison report - H200 SGLang vs vLLM entry added to root README	2026-07-08 07:34:34 +00:00