This file provides guidance to Coding Agent when working with code in this repository.
Pure Rust + CUDA LLM inference engine. No PyTorch, no frameworks. OpenAI-compatible /v1/completions API.
Supported models:
Every model line is behind a cargo feature; only qwen3 is a default feature, so the stock build is pure Rust + CUDA with no Python.
| Model | Crate | Feature flag | Architecture |
|---|---|---|---|
| Qwen3-4B / 8B | pegainfer-qwen3 |
qwen3 (default) |
Full attention, TP support |
| Qwen3.5-4B / 9B / 27B · Qwen3.8-27B | pegainfer-qwen35 |
--features qwen35 (needs build-time Python + Triton) |
Hybrid Gated DeltaNet + full attention. Qwen3.8 shares the line: same model_type, same text geometry — see docs/models/qwen35/support-qwen38.md |
| DeepSeek-V2-Lite | pegainfer-deepseek-v2-lite |
--features deepseek-v2-lite |
MoE + EP, 2-GPU |
| Gemma 4 | pegainfer-gemma4 |
--features gemma4 |
Sliding-window + global full attention, single GPU, batched decode, opt-in chunked prefill |
| Kimi-K2 | pegainfer-kimi-k2 |
--features kimi-k2 |
MLA + MoE + Marlin INT4, 8-GPU EP |
| GLM5.2 | pegainfer-glm52 |
--features glm52 |
MLA + MoE + FP8, 8-GPU EP (bring-up) |
| Kimi-K3 | pegainfer-k3 |
--features k3 |
Hybrid KDA + MLA, latent MoE + MXFP4, EP (bring-up — single-rank decode wired) |
Always use --release — debug builds are extremely slow for GPU/CUDA and will timeout.
When developing with Docker, use docker/Dockerfile.dev and docker/dev.sh as described in docker/README.md.
# Qwen3 (default feature, no Python anywhere in the build)
cargo run --release -- --model-path models/Qwen3-4B
# Feature-gated models
cargo run --release --features qwen35 -- --model-path models/Qwen3.5-4B
cargo run --release --features kimi-k2 -- --model-path models/Kimi-K2
cargo run --release --features deepseek-v2-lite -- --model-path models/DeepSeek-V2-Lite
cargo run --release --features glm52 -- --model-path models/GLM5.2Key env vars:
PEGAINFER_CUDA_SM— GPU SM target override whennvidia-smiunavailable (e.g.120or120,80)PEGAINFER_TRITON_PYTHON— Python with Triton forqwen35build-time AOT kernel generation (falls back to.venv/bin/python, thenpython3, thenpython)PEGAINFER_TILELANG_PYTHON— Python with TileLang for theglm52sparse-MLA build-time AOT (sm_90a targets only)PEGAINFER_NCCL_ROOT— NCCL root (>= 2.30.4) for DeepEP shim (moefeature)PEGAINFER_FLASHINFER_INCLUDE— FlashInfer include dir overridePEGAINFER_TEST_MODEL_PATH— override test model path (default:models/Qwen3-4B)PEGAINFER_BUILD_TIMING=1— print per-phase build timings (nvcc, Triton AOT, etc.)PEGAINFER_NVCC_JOBS— override parallel nvcc job countPEGAINFER_GEMM_LT_CACHE— opt-in cross-process cublasLt algo store:<file>carries the winnersgemm_lt_tunetimed in an earlier boot instead of re-timing them (Qwen3-4B on one sm_89 card: warm ready ~1965 → ~1312 ms, paired 5/5). Append-only text, created if absent, safe to share between processes and machines and safe to delete; each record carries GPU, CUDA runtime/driver/cublasLt version, shape and workspace cap, so anything that does not match is a miss and re-tunes (a driver update that keeps the same CUDA level is not distinguished — delete the file to force a re-tune). Unset = tune on every boot; Qwen3's--batch-invariantpins the heuristic instead and never reads itPEGAINFER_GLOBAL_ATTN— gemma4 global-attention kernel and pool format: unset/off= the incumbent kernel on the split K|V pool (byte-identical serving);tilelang= the generated kernel on the same pool;tilelang640= the generated kernel on a folded pool whose rows hold K only where the rotation touches it and fold K's norm weight into the query, 640 columns per token per head instead of 1024. Both generated states also read the sliding family's prompt rows through a generated windowed prefill and its pure-decode rows through a generated windowed split-KV kernel, project Q|K|V and gate|up with one GEMM each where the split state issues one per projection (the fused shape may round differently), need a build that carries the kernels, and report the global pool's bytes at start-upPEGAINFER_KV_FP8— gemma4 opt-in fp8 KV:localstores the sliding family's K/V as e4m3 at scale 1.0 (lossy; halves the local pool; refuses an enabled prefix cache; unset = byte-identical serving)PEGAINFER_PREFIX_CACHE— gemma4 opt-in conversation prefix cache:Kentries of captured prompt state resume multi-turn prompts (pre-allocated page budget; unset = off, byte-identical serving)PEGAINFER_ADMIT_COALESCE_MS— gemma4 opt-in admission coalesce door:Nms in1..=2000(off/0/unset = admit on sight), holds arrivals that would invade a live decode batch so a window's arrivals land as one admission burst; refuses the async prefill lane; merging into one mixed step needs the chunked walk or a sub-budget promptPEGAINFER_ASYNC_PREFILL— gemma4 opt-in overlap lane:green:NNprefills live-batch admissions on an SM-capped stream to protect decode tails (sharedfor comparison; unset = off; bad values refuse to start)PEGAINFER_MIX_CHUNK_TOKENS— gemma4 opt-in chunked walk: a mixed admission computes at mostNprompt rows per step (64 <= N <the serving ceiling; unset = whole-prompt steps; bad values refuse to start)PEGAINFER_MIX_GATHER_ROWS/PEGAINFER_MIX_MAX_PROMPTS— gemma4 admission gather: how many prompt rows and how many prompts one mixed step may absorb (1..=the serving ceiling and1..=the decode slots; defaults gather only short bursts). Raising them lets a burst ride one step, which trades the median time to first token for the p99 tail and the wide-batch decode step; bad values refuse to startPEGAINFER_MAX_CONTEXT— gemma4 serving ceiling raise (default 8192, up to the checkpoint's 262144; a raise past the default needsPEGAINFER_MIX_CHUNK_TOKENSand refuses the async lane)PEGAINFER_DECODE_SLOTS— gemma4 decode slots (1..16, default 16): global KV budget = slots x ceiling, trade concurrency for contextGLM52_DECODE_SLOTS/GLM52_MTP_DRAFTS— glm52 runtime profile: decode slots per rank (default 8, ceiling 32) and MTP draft span (default 5);slots x (1+drafts)must fit the 96-row step (validated at launch; MTP only). Throughput ceiling profile:32/2.PEGAINFER_K3_CP— k3 opt-in context-parallel prefill lane: CP width, must equal the process's local rank count (on a fleet each process runs its own gang; remote ranks pad). Mutually exclusive with the dspark draft lane.PEGAINFER_K3_CP_MIN— k3 CP admission floor in prompt tokens (default 2048; measured crossover ~1k). Prompts below it, or too long for one chunk step per rank (M0), prefill locally.
# Unit tests (~9s)
cargo test --release --workspace --lib
# Accuracy and integration tests — require GPU + model weights
cargo test --release -p pegainfer-qwen3 --test hf_golden_gate
PEGAINFER_TEST_MODEL_PATH=models/Qwen3.5-4B cargo test --release -p pegainfer-qwen35 --features qwen35 --test hf_golden_gate
PEGAINFER_TEST_MODEL_PATH=models/Qwen3.5-4B cargo test --release -p pegainfer-qwen35 --features qwen35 --test e2e_scheduler
# Single test (filter by name)
cargo test --release --workspace --lib prefix_cache -- --nocaptureQwen accuracy gates compare logits against stored HF golden fixtures. Qwen3.5 exact-text JSON baselines are retired; keep e2e_scheduler for scheduler liveness and request-flow coverage.
HTTP Request → vLLM frontend → EngineHandle → per-model scheduler/executor → TokenEvent
│
┌──────────┬─────────────┬───────┼───────────┬──────────┐
│ │ │ │ │ │
pegainfer- pegainfer- pegainfer- pegainfer- pegainfer- ...
qwen3 qwen35 dsv2-lite kimi-k2 glm52
(full attn) (linear+full) (MoE+EP) (MLA+MoE) (MLA+MoE+FP8)
│ │ │ │ │ │
└──────────┴─────────────┴───────┼───────────┴──────────┘
│
pegainfer-core runtime + pegainfer-kernels
│
┌───────────────┼───────────────┐
│ │ │
CUDA / cuBLAS Triton AOT FlashInfer
(sampling, attention,
norm, MLA decode)
Key abstractions:
pegainfer-frontend— the serving frontend: the engine request/event contract (pegainfer_frontend::engine—EngineHandle,GenerateRequest,TokenEvent) plus the protocol stacks on top of it (vllmmodule today,dynamoplanned) and theModelLinedispatch trait. Model crates implement against the contract; the server binary does pure dispatch.- Per-model crates — each model owns config, weights, prefill/decode execution, scheduler, tests, and benches.
pegainfer-core::ops— shared GPU operator wrappers used by model crates.pegainfer-kernels— tensor/FFI/kernel build owner for CUDA, cuBLAS, FlashInfer, and Triton AOT. Model-specific kernels live in feature-gated submodules (kimi_k2,glm52).- CUDA Graph — decode path captured inside model executors with pre-allocated buffers to preserve pointer stability.
- KV state — model schedulers own request state; shared paged-KV primitives live in
pegainfer-kv-cache; host/SSD/RDMA offload bridge inpegainfer-kv-offload.
Build system: the virtual workspace root has no package build script. pegainfer-kernels/build.rs owns CUDA/Triton compilation:
- Compiles
pegainfer-kernels/csrc/*.cuwith nvcc (auto-detects GPU SM targets) - Feature-gated codegen:
qwen35runs Triton AOT viapegainfer-kernels/tools/triton/gen_triton_aot.py;kimi-k2adds MLA/MoE/Marlin CUDA;glm52adds MLA/MoE/FP8 CUDA plus TileLang sparse-MLA codegen on sm_90a
Canonical doc: docs/models/glm52/free-running-dp.md (K3's gang lane follows it). Invariants — violating any of these is a deadlock design:
- No rank ever stops or waits. Every engine loop runs unconditionally at full speed; idle ranks step with padding rows. Any quiet wait (condvar, sleep-poll) inside EP coordination is a bug, and the fleet is never asleep, so never design "wake up" or "pump until X" steps.
- The per-step collective chain is fixed — no conditional collectives. Skipping work happens inside kernels via zero-load padding entry, never by host negotiation.
- The launch count is the global clock (pairing pins all ranks within ±1 launch). Coordination means agreeing ahead of time on what step N contains, never "wait until everyone is ready".
- Padding rows are protocol surface: their bytes reach peers, so every dummy-row input must be constructively deterministic.
AI-assisted PRs must be accountable and verifiable. Show that the work is not duplicated, name the production invariant being changed, and provide real evidence: production E2E for features and fixes, same-context A/B for performance, and model evals for output or accuracy changes. Every changed file must serve that invariant; remove unrelated cleanup, thin wrappers, generated scaffolding, and mock or source-text tests presented as production evidence.
Collaboration centered on the docs/ directory.
Docs are organized by what they're about, not by lifecycle stage. A doc's freshness lives in its TL;DR (and Last touched: for active areas) — not by which directory it sits in. Completed work stays co-located with its domain. There is no archives/ directory — if a doc no longer earns its keep, delete it; if a lasting lesson hides inside it, lift that lesson into lessons/ first, then delete.
docs/
├── index.md # Routing table — every doc must be listed here
├── roadmap/ # Strategic plans, quarterly direction, milestones
├── models/<line>/ # Per-model living docs (qwen3, qwen35, kimi-k2, ...)
│ # — design, accuracy, perf, refactor records, gotchas
├── subsystems/<area>/ # Cross-cutting components (runtime, scheduler, frontend, kernels)
├── playbooks/ # Reusable how-to: benching, profiling, accuracy, onboarding
├── lessons/ # Tribal knowledge from research / other projects
├── benchmarks/ # Standalone benchmark snapshots and eval reports
├── conventions/ # Ongoing standards (bench regression, coding style)
└── private/ # Local-only notes (gitignored)
Classification rule at capture time:
- Is it tied to a specific model? →
models/<line>/ - A specific subsystem? →
subsystems/<area>/ - Reusable how-to applicable across models? →
playbooks/ - Lasting lesson from elsewhere (other repo, research, postmortem)? →
lessons/ - Snapshot of measurement, not a doc that evolves? →
benchmarks/ - Strategic / cross-cutting plan? →
roadmap/
If you can't pick one, the doc probably needs splitting.
- Docs cover what
--helpand code can't: pitfalls, diagnostic paths, decision context. Don't restate CLI reference. - Every command in a doc must be run and verified before committing. Unverified commands are technical debt.
- The only required header is a one-line TL;DR. Keep it true; that's the contract.
- For
models/<line>/andsubsystems/<area>/docs, addLast touched: YYYY-MMand bump it when you do meaningful work on the doc (not for typo fixes). The date is a fact, not a judgement — readers infer freshness themselves. playbooks/,lessons/,conventions/,roadmap/,benchmarks/,archives/don't need a freshness stamp. They're either timeless until disproven, or self-dated, or explicitly inert.- No
Status:enum. Enum fields go stale exactly when you need them most.
index.md is a routing table with a scanning-friendly TL;DR column. It is allowed to drift from the TL;DR inside each doc — the doc body is authoritative. Update index.md when you create or delete a doc, or when the existing TL;DR is so wrong it actively misleads. Don't churn it on every doc edit.
Documentation exists to advance work, not to hoard information. Four steps when handling information:
- Capture: Only record what materially advances the project. When in doubt, leave it out.
- Organize: Action-oriented. Resist the urge to organize for organization's sake — structure should be just enough.
- Distill: Refactor over append. When you learn something new or hit a pitfall, integrate it into the document body — don't pile a changelog at the bottom.
- Express: Every document must point to a next step. Split unwieldy documents proactively. Active documents must note the current blocker or next action.
Sync
At the start of each session, you must read index.md and load the documents needed for the task at hand.
Execute
- Update relevant documents as you go. When a new problem or idea arises, create a document in the appropriate domain directory (see classification rule above).
- Record why a decision was made, not just what was done.
Commit
When a session wraps up:
- Update the TL;DR (and
Last touched, where applicable) at the top of each modified document. - Update
index.mdonly when you created or deleted a doc, or when its TL;DR row is now misleading (see Drift Policy above).
Commit messages use Commitizen format: <type>(<scope>): <subject>. Never commit directly to main — create a feat//fix//chore//… branch first.
CI runs cargo fmt --check; run cargo fmt before committing.