For large bs (production target: bs~10 x ~100k tokens), per-layer granularity does 10x79 = 790 submitTransfer calls + CUDA events + enqueues per forward on the forward thread. Two overhead cuts: - Group SGLANG_CP_SHARED_KV_PER_LAYER_GROUP (default 8) consecutive layers into ONE RDMA submit: ~num_layers/K submits + events + enqueues instead of per-layer; same bytes (page index lists are identical across layers). on_layer_end is O(1) at non-boundary layers. The last partial group enqueues via the num_layers boundary; any misses fall back to one batched sync submit. - Scheduler hook skips reqs already registered (bs>1 batch-forming re-iterates the same reqs ~9x -> was rebuilding the CP filter + context every time). 27 unit tests pass incl. grouping-boundary + batched-fallback. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Registered Tests
Tests under this directory are auto-discovered by run_suite.py via CI registration decorators.
Where Should I Put My New Test?
No server / engine launch required
| What you're testing | Directory | Requires |
|---|---|---|
| Component logic in isolation (cache, scheduler, config, parser, etc.) | unit/<module>/ |
CPU or GPU |
| CUDA kernel correctness | kernels/ |
GPU |
Server / engine launch required (E2E)
| What you're testing | Directory | Requires |
|---|---|---|
| Model inference correctness | models/, 4-gpu-models/, 8-gpu-models/ |
GPU |
| Feature-specific (OpenAI API, LoRA, speculative, distributed, VLM, etc.) | openai_server/, lora/, spec/, distributed/, ... |
GPU |
| Benchmarks (performance, accuracy, stress) | benchmark/ |
GPU |
| Platform-specific | amd/, ascend/ |
Vendor GPU |
See unit/README.md for unit test conventions.