History

Quantong Qiu a5d69dfd9a docs(h200): H200 quick-start guide, porting workflow, and example experiment

- Update platforms/nvidia_h200.env with ENGINE and configurable venv/paths.
- Update platforms/README.md with H200 notes and platform-addition guide.
- Add docs/H200_QUICKSTART.md with concrete H200 usage steps.
- Add experiments/dsv4_h200_dspark/ as a migration wrapper around the
  existing scripts/benchmark_dspark_0707/ grid benchmark, writing results
  into the new experiments/<name>/results/<RUN_ID>/ layout.
- Update BENCHMARK_WORKFLOW.md with a 'Adding a New Platform or Experiment'
  section and mention the H200 wrapper in Quick Start.
- Update main README.md to index the H200 experiment and link to the guide.

2026-07-08 05:55:11 +00:00

patches/kunlun_p800

refactor: experiments/ + platforms/ layout and P800 SGLang support

2026-07-08 05:15:59 +00:00

kunlun_p800.env

refactor: experiments/ + platforms/ layout and P800 SGLang support

2026-07-08 05:15:59 +00:00

nvidia_h200.env

docs(h200): H200 quick-start guide, porting workflow, and example experiment

2026-07-08 05:55:11 +00:00

README.md

docs(h200): H200 quick-start guide, porting workflow, and example experiment

2026-07-08 05:55:11 +00:00

README.md

Platform Configurations

Each .env file in this directory describes one accelerator platform. They are meant to be sourced by benchmark scripts through scripts/common/platform.sh, not executed directly.

Usage

# Default platform for the current machine
bash experiments/dsv4_p800_sglang/run_bench.sh

# Explicitly select a platform
PLATFORM=kunlun_p800 bash experiments/dsv4_p800_sglang/run_bench.sh

Current platforms

File	Chip/Accelerator	Engine	Notes
`kunlun_p800.env`	Kunlun P800 XPU	`sglang-xpu`	Docker-based SGLang serving image
`nvidia_h200.env`	NVIDIA H200	`vllm-dspark`	Native host virtual environments

What belongs here

Chip/accelerator identity (CHIP, ACCELERATOR, HARDWARE, ENGINE).
Device selection environment variables.
Platform-wide paths that rarely change (model root, default port).
Container image / interpreter paths for Docker-based platforms.
Native interpreter / venv paths for host-based platforms.

What does NOT belong here

Specific model names or experiment scenarios — those go in experiments/<name>/config.env.
Engine-specific launch flags — those go in the experiment's start_server.sh or run_bench.sh.

Adding a new platform

Create platforms/<chip>.env with at least CHIP, ACCELERATOR, HARDWARE, ENGINE, DEFAULT_PORT, MODEL_ROOT.
If the platform runs inside Docker, set DOCKER_IMAGE, CONTAINER_NAME, CONTAINER_PYTHON, and PATCH_ROOT (see kunlun_p800.env).
If the platform runs natively on the host, set the relevant venv paths (see nvidia_h200.env).
Add a row to the table above and write a quick-start experiment under experiments/<name>/.