pi-usereq 0.49.0 → 0.50.0

package/docs/pi.dev/pods-docs/gpt-oss.md

@@ -1,233 +0,0 @@
-## `gpt-oss` vLLM Usage Guide
-
-`gpt-oss-20b` and `gpt-oss-120b` are powerful reasoning models open-sourced by OpenAI.
-In vLLM, you can run it on NVIDIA H100, H200, B200 as well as MI300x, MI325x, MI355x and Radeon AI PRO R9700.
-We are actively working on ensuring this model can work on Ampere, Ada Lovelace, and RTX 5090.
-Specifically, vLLM optimizes for `gpt-oss` family of models with
-
-* **Flexible parallelism options**: the model can be sharded across 2, 4, 8 GPUs, scaling throughput.
-* **High performance attention and MoE kernels**: attention kernel is specifically optimized for the attention sinks mechanism and sliding window shapes.
-* **Asynchronous scheduling**: optimizing for maximum utilization and high throughput by overlapping CPU operations with GPU operations.
-
-This is a living document and we welcome contributions, corrections, and creation of new recipes!
-
-## Quickstart
-
-### Installation
-
-We highly recommend using a new virtual environment, as the first iteration of the release requires cutting edge kernels from various dependencies, these might not work with other models. In particular, we will be installing: a prerelease version of vLLM, PyTorch nightly, Triton nightly, FlashInfer prerelease, HuggingFace prerelease, Harmony, and gpt-oss library tools.
-
-```
-uv venv
-source .venv/bin/activate
-
-uv pip install --pre vllm==0.10.1+gptoss \
-    --extra-index-url https://wheels.vllm.ai/gpt-oss/ \
-    --extra-index-url https://download.pytorch.org/whl/nightly/cu128 \
-    --index-strategy unsafe-best-match
-```
-
-We also provide a docker container with all the dependencies built in
-
-```
-docker run --gpus all \
-    -p 8000:8000 \
-    --ipc=host \
-    vllm/vllm-openai:gptoss \
-    --model openai/gpt-oss-20b
-```
-
-### H100 & H200
-
-You can serve the model with its default parameters:
-
-* `--async-scheduling` can be enabled for higher performance. Currently it is not compatible with structured output.
-* We recommend TP=2 for H100 and H200 as the best performance tradeoff point.
-
-```
-# openai/gpt-oss-20b should run in single GPU
-vllm serve openai/gpt-oss-20b --async-scheduling
-
-# gpt-oss-120b will fit in a single H100/H200, but scaling it to higher TP sizes can help with throughput
-vllm serve openai/gpt-oss-120b --async-scheduling
-vllm serve openai/gpt-oss-120b --tensor-parallel-size 2 --async-scheduling
-vllm serve openai/gpt-oss-120b --tensor-parallel-size 4 --async-scheduling
-```
-
-### B200
-
-NVIDIA Blackwell requires installation of FlashInfer library and several environments to enable the necessary kernels. We recommend TP=1 as a starting point for a performant option. We are actively working on the performance of vLLM on Blackwell.
-
-```
-# All 3 of these are required
-export VLLM_USE_TRTLLM_ATTENTION=1
-export VLLM_USE_TRTLLM_DECODE_ATTENTION=1
-export VLLM_USE_TRTLLM_CONTEXT_ATTENTION=1
-
-# Pick only one out of the two.
-# mxfp8 activation for MoE. faster, but higher risk for accuracy.
-export VLLM_USE_FLASHINFER_MXFP4_MOE=1
-# bf16 activation for MoE. matching reference precision.
-export VLLM_USE_FLASHINFER_MXFP4_BF16_MOE=1
-
-# openai/gpt-oss-20b
-vllm serve openai/gpt-oss-20b --async-scheduling
-
-# gpt-oss-120b
-vllm serve openai/gpt-oss-120b --async-scheduling
-vllm serve openai/gpt-oss-120b --tensor-parallel-size 2 --async-scheduling
-vllm serve openai/gpt-oss-120b --tensor-parallel-size 4 --async-scheduling
-```
-
-### AMD
-
-ROCm supports OpenAI gpt-oss-120b or gpt-oss-20b models on these 3 different GPUs on day one, along with the pre-built docker containers:
-
-* gfx950: MI350x series, `rocm/vllm-dev:open-mi355-08052025`
-* gfx942: MI300x/MI325 series, `rocm/vllm-dev:open-mi300-08052025`
-* gfx1201: Radeon AI PRO R9700, `rocm/vllm-dev:open-r9700-08052025`
-
-To run the container:
-
-```
-alias drun='sudo docker run -it --network=host --device=/dev/kfd --device=/dev/dri --group-add=video --ipc=host --cap-add=SYS_PTRACE --security-opt seccomp=unconfined --shm-size 32G -v /data:/data -v $HOME:/myhome -w /myhome'
-
-drun rocm/vllm-dev:open-mi300-08052025
-```
-
-For MI300x and R9700:
-
-```
-export VLLM_ROCM_USE_AITER=1
-export VLLM_USE_AITER_UNIFIED_ATTENTION=1
-export VLLM_ROCM_USE_AITER_MHA=0
-
-vllm serve openai/gpt-oss-120b --compilation-config '{"full_cuda_graph": true}'
-```
-
-For MI355x:
-
-```
-# MoE preshuffle, fusion and Triton GEMM flags
-export VLLM_USE_AITER_TRITON_FUSED_SPLIT_QKV_ROPE=1
-export VLLM_USE_AITER_TRITON_FUSED_ADD_RMSNORM_PAD=1
-export VLLM_USE_AITER_TRITON_GEMM=1
-export VLLM_ROCM_USE_AITER=1
-export VLLM_USE_AITER_UNIFIED_ATTENTION=1
-export VLLM_ROCM_USE_AITER_MHA=0
-export TRITON_HIP_PRESHUFFLE_SCALES=1
-
-vllm serve openai/gpt-oss-120b --compilation-config '{"compile_sizes": [1, 2, 4, 8, 16, 24, 32, 64, 128, 256, 4096, 8192], "full_cuda_graph": true}' --block-size 64
-```
-
-## Usage
-
-Once the `vllm serve` runs and `INFO: Application startup complete` has been displayed, you can send requests using HTTP request or OpenAI SDK to the following endpoints:
-
-* `/v1/responses` endpoint can perform tool use (browsing, python, mcp) in between chain-of-thought and deliver a final response. This endpoint leverages the `openai-harmony` library for input rendering and output parsing. Stateful operation and full streaming API are work in progress. Responses API is recommended by OpenAI as the way to interact with this model.
-* `/v1/chat/completions` endpoint offers a familiar interface to this model. No tool will be invoked but reasoning and final text output will be returned structurally. Function calling is work in progress. You can also set the parameter `include_reasoning: false` in request parameter to skip CoT being part of the output.
-* `/v1/completions` endpoint is the endpoint for a simple input output interface without any sorts of template rendering.
-
-All endpoints accept `stream: true` as part of the operations to enable incremental token streaming. Please note that vLLM currently does not cover the full scope of responses API, for more detail, please see Limitation section below.
-
-### Tool Use
-
-One premier feature of gpt-oss is the ability to call tools directly, called "built-in tools". In vLLM, we offer several options:
-
-* By default, we integrate with the reference library's browser (with `ExaBackend`) and demo Python interpreter via docker container. In order to use the search backend, you need to get access to [exa.ai](http://exa.ai) and put `EXA_API_KEY=` as an environment variable. For Python, either have docker available, or set `PYTHON_EXECUTION_BACKEND=UV` to dangerously allow execution of model generated code snippets to be executed on the same machine.
-
-```
-uv pip install gpt-oss
-
-vllm serve ... --tool-server demo
-```
-
-* Please note that the default options are simply for demo purposes. For production usage, vLLM itself can act as MCP client to multiple services.
-Here is an [example tool server](https://github.com/openai/gpt-oss/tree/main/gpt-oss-mcp-server) that vLLM can work with, they wrap the demo tools:
-
-```
-mcp run -t sse browser_server.py:mcp
-mcp run -t sse python_server.py:mcp
-
-vllm serve ... --tool-server ip-1:port-1,ip-2:port-2
-```
-
-The URLs are expected to be MCP SSE servers that implement `instructions` in server info and well documented tools. The tools will be injected into the system prompt for the model to enable them.
-
-## Accuracy Evaluation Panels
-
-OpenAI recommends using the gpt-oss reference library to perform evaluation. For example,
-
-```
-python -m gpt_oss.evals --model 120b-low --eval gpqa --n-threads 128
-python -m gpt_oss.evals --model 120b --eval gpqa --n-threads 128
-python -m gpt_oss.evals --model 120b-high --eval gpqa --n-threads 128
-```
-To eval on AIME2025, change `gpqa` to `aime25`.
-With vLLM deployed:
-
-```
-# Example deployment on 8xH100
-vllm serve openai/gpt-oss-120b \
-  --tensor_parallel_size 8 \
-  --max-model-len 131072 \
-  --max-num-batched-tokens 10240 \
-  --max-num-seqs 128 \
-  --gpu-memory-utilization 0.85 \
-  --no-enable-prefix-caching
-```
-
-Here is the score we were able to reproduce without tool use, and we encourage you to try reproducing it as well!
-We’ve observed that the numbers may vary slightly across runs, so feel free to run the evaluation multiple times to get a sense of the variance.
-For a quick correctness check, we recommend starting with the low reasoning effort setting (120b-low), which should complete within minutes.
-
-Model: 120B
-
-| Reasoning Effort | GPQA | AIME25 |
-| :---- | :---- | :---- |
-| Low  | 65.3 | 51.2 |
-| Mid  | 72.4 | 79.6 |
-| High  | 79.4 | 93.0 |
-
-Model: 20B
-
-| Reasoning Effort | GPQA | AIME25 |
-| :---- | :---- | :---- |
-| Low  | 56.8 | 38.8 |
-| Mid  | 67.5 | 75.0 |
-| High  | 70.9 | 85.8  |
-
-## Known Limitations
-
-* On H100 using tensor parallel size 1, default gpu memory utilization, and batched token will cause CUDA Out-of-memory. When running tp1, please increase your gpu memory utilization or lower batched token
-
-```
-vllm serve openai/gpt-oss-120b --gpu-memory-utilization 0.95 --max-num-batched-tokens 1024
-```
-
-* When running TP2 on H100, set your gpu memory utilization below 0.95 as that will also cause OOM
-* Responses API has several limitations at the current moment; we strongly welcome contribution and maintenance of this service in vLLM
-* Usage accounting is currently broken and only returns all zeros.
-* Annotations (citing URLs from search results) are not supported.
-* Truncation by `max_tokens` might not be able to preserve partial chunks.
-* Streaming is fairly barebone at the moment, for example:
-  * Item id and indexing needs more work
-  * Tool invocation and output are not properly streamed, rather batched.
-  * Proper error handling is missing.
-
-## Troubleshooting
-
-- Attention sink dtype error on Blackwell:
-
-```
-  ERROR 08-05 07:31:10 [multiproc_executor.py:559]     assert sinks.dtype == torch.float32, "Sinks must be of type float32"
-  **(VllmWorker TP0 pid=174579)** ERROR 08-05 07:31:10 [multiproc_executor.py:559]            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-  **(VllmWorker TP0 pid=174579)** ERROR 08-05 07:31:10 [multiproc_executor.py:559] AssertionError: Sinks must be of type float32
-```
-
-**Solution: Please refer to Blackwell section to check if related environment variables are added.**
-
-- Triton issue related to `tl.language` not defined:
-
-**Solution: Make sure there's no other triton installed in your environment (pytorch-triton, etc).**
-

package/docs/pi.dev/pods-docs/implementation-plan.md

@@ -1,183 +0,0 @@
-# Implementation Plan
-
-## Core Principles
-- TypeScript throughout
-- Clean, minimal code
-- Self-contained modules
-- Direct SSH execution (no remote manager)
-- All state in local JSON
-
-## Package 1: Pod Setup Script Generation
-Generate and execute pod_setup.sh via SSH
-
-- [ ] `src/setup/generate-setup-script.ts` - Generate bash script as string
-  - [ ] Detect CUDA driver version
-  - [ ] Determine CUDA toolkit version needed
-  - [ ] Generate uv/Python install commands
-  - [ ] Generate venv creation commands
-  - [ ] Generate pip install commands (torch, vLLM, etc.)
-  - [ ] Handle model-specific vLLM versions (e.g., gpt-oss needs 0.10.1+gptoss)
-  - [ ] Generate mount commands if --mount provided
-  - [ ] Generate env var setup (HF_TOKEN, PI_API_KEY)
-
-- [ ] `src/setup/detect-hardware.ts` - Run nvidia-smi and parse GPU info
-  - [ ] Execute nvidia-smi via SSH
-  - [ ] Parse GPU count, names, memory
-  - [ ] Return structured GPU info
-
-- [ ] `src/setup/execute-setup.ts` - Main setup orchestrator
-  - [ ] Generate setup script
-  - [ ] Copy and execute via SSH
-  - [ ] Stream output to console
-  - [ ] Handle Ctrl+C properly
-  - [ ] Save GPU info to local config
-
-## Package 2: Config Management
-Local JSON state management
-
-- [ ] `src/config/types.ts` - TypeScript interfaces
-  - [ ] Pod interface (ssh, gpus, models, mount)
-  - [ ] Model interface (model, port, gpu, pid)
-  - [ ] GPU interface (id, name, memory)
-
-- [ ] `src/config/store.ts` - Read/write ~/.pi/pods.json
-  - [ ] Load config (handle missing file)
-  - [ ] Save config (atomic write)
-  - [ ] Get active pod
-  - [ ] Add/remove pods
-  - [ ] Update model state
-
-## Package 3: SSH Executor
-Clean SSH command execution
-
-- [ ] `src/ssh/executor.ts` - SSH command wrapper
-  - [ ] Execute command with streaming output
-  - [ ] Execute command with captured output
-  - [ ] Handle SSH errors gracefully
-  - [ ] Support Ctrl+C propagation
-  - [ ] Support background processes (nohup)
-
-## Package 4: Pod Commands
-Pod management CLI commands
-
-- [ ] `src/commands/pods-setup.ts` - pi pods setup
-  - [ ] Parse args (name, ssh, mount)
-  - [ ] Check env vars (HF_TOKEN, PI_API_KEY)
-  - [ ] Call setup executor
-  - [ ] Save pod to config
-
-- [ ] `src/commands/pods-list.ts` - pi pods
-  - [ ] Load config
-  - [ ] Display all pods with active marker
-
-- [ ] `src/commands/pods-active.ts` - pi pods active
-  - [ ] Switch active pod
-  - [ ] Update config
-
-- [ ] `src/commands/pods-remove.ts` - pi pods remove
-  - [ ] Remove from config (not remote)
-
-## Package 5: Model Management
-Model lifecycle management
-
-- [ ] `src/models/model-config.ts` - Known model configurations
-  - [ ] Load models.md data structure
-  - [ ] Match hardware to vLLM args
-  - [ ] Get model-specific env vars
-
-- [ ] `src/models/download.ts` - Model download via HF
-  - [ ] Check if model cached
-  - [ ] Run huggingface-cli download
-  - [ ] Stream progress to console
-  - [ ] Handle Ctrl+C
-
-- [ ] `src/models/vllm-builder.ts` - Build vLLM command
-  - [ ] Get base command for model
-  - [ ] Add hardware-specific args
-  - [ ] Add user --vllm args
-  - [ ] Add port and API key
-
-## Package 6: Model Commands
-Model management CLI commands
-
-- [ ] `src/commands/start.ts` - pi start
-  - [ ] Parse model and args
-  - [ ] Find next available port
-  - [ ] Select GPU (round-robin)
-  - [ ] Download if needed
-  - [ ] Build and execute vLLM command
-  - [ ] Wait for health check
-  - [ ] Update config on success
-
-- [ ] `src/commands/stop.ts` - pi stop
-  - [ ] Find model in config
-  - [ ] Kill process via PID
-  - [ ] Clean up config
-
-- [ ] `src/commands/list.ts` - pi list
-  - [ ] Show models from config
-  - [ ] Optionally verify PIDs
-
-- [ ] `src/commands/logs.ts` - pi logs
-  - [ ] Tail log file via SSH
-  - [ ] Handle Ctrl+C (stop tailing only)
-
-## Package 7: Model Testing
-Quick model testing with tools
-
-- [ ] `src/prompt/tools.ts` - Tool definitions
-  - [ ] Define ls, read, glob, rg tools
-  - [ ] Format for OpenAI API
-
-- [ ] `src/prompt/client.ts` - OpenAI client wrapper
-  - [ ] Create client for model endpoint
-  - [ ] Handle streaming responses
-  - [ ] Display thinking, tools, content
-
-- [ ] `src/commands/prompt.ts` - pi prompt
-  - [ ] Get model endpoint from config
-  - [ ] Augment prompt with CWD info
-  - [ ] Send request with tools
-  - [ ] Display formatted response
-
-## Package 8: CLI Entry Point
-Main CLI with commander.js
-
-- [ ] `src/cli.ts` - Main entry point
-  - [ ] Setup commander program
-  - [ ] Register all commands
-  - [ ] Handle global options (--pod override)
-  - [ ] Error handling
-
-- [ ] `src/index.ts` - Package exports
-
-## Testing Strategy
-- [ ] Test pod_setup.sh generation locally
-- [ ] Test on local machine with GPU
-- [ ] Test SSH executor with mock commands
-- [ ] Test config management with temp files
-- [ ] Integration test on real pod
-
-## Dependencies
-```json
-{
-  "dependencies": {
-    "commander": "^12.0.0",
-    "@commander-js/extra-typings": "^12.0.0",
-    "openai": "^4.0.0",
-    "chalk": "^5.0.0",
-    "ora": "^8.0.0"
-  },
-  "devDependencies": {
-    "@types/node": "^22.0.0",
-    "typescript": "^5.0.0",
-    "tsx": "^4.0.0"
-  }
-}
-```
-
-## Build & Distribution
-- [ ] TypeScript config for Node.js target
-- [ ] Build to dist/
-- [ ] npm package with bin entry
-- [ ] npx support

package/docs/pi.dev/pods-docs/kimi-k2.md

@@ -1,197 +0,0 @@
-# Kimi-K2 Deployment Guide
-
-> [!Note]
-> This guide only provides some examples of deployment commands for Kimi-K2, which may not be the optimal configuration. Since inference engines are still being updated frequently,  please continue to follow the guidance from their homepage if you want to achieve better inference performance.
-
-
-## vLLM Deployment
-vLLM version v0.10.0rc1 or later is required.
-
-The smallest deployment unit for Kimi-K2 FP8 weights with 128k seqlen on mainstream H200 or H20 platform is a cluster with 16 GPUs with either Tensor Parallel (TP) or "data parallel + expert parallel" (DP+EP).
-Running parameters for this environment are provided below. You may scale up to more nodes and increase expert-parallelism to enlarge the inference batch size and overall throughput.
-
-### Tensor Parallelism
-
-When the parallelism degree ≤ 16, you can run inference with pure Tensor Parallelism. A sample launch command is:
-
-``` bash
-# start ray on node 0 and node 1
-
-# node 0:
-vllm serve $MODEL_PATH \
-  --port 8000 \
-  --served-model-name kimi-k2 \
-  --trust-remote-code \
-  --tensor-parallel-size 16 \
-  --enable-auto-tool-choice \
-  --tool-call-parser kimi_k2
-```
-
-**Key parameter notes:**
-- `--tensor-parallel-size 16`: If using more than 16 GPUs, combine with pipeline-parallelism.
-- `--enable-auto-tool-choice`: Required when enabling tool usage.
-- `--tool-call-parser kimi_k2`: Required when enabling tool usage.
-
-### Data Parallelism + Expert Parallelism
-
-You can install libraries like DeepEP and DeepGEMM as needed. Then run the command (example on H200):
-
-``` bash
-# node 0
-vllm serve $MODEL_PATH --port 8000 --served-model-name kimi-k2 --trust-remote-code --data-parallel-size 16 --data-parallel-size-local 8 --data-parallel-address $MASTER_IP --data-parallel-rpc-port $PORT --enable-expert-parallel --max-num-batched-tokens 8192 --max-num-seqs 256 --gpu-memory-utilization 0.85 --enable-auto-tool-choice --tool-call-parser kimi_k2
-
-# node 1
-vllm serve $MODEL_PATH --headless --data-parallel-start-rank 8 --port 8000 --served-model-name kimi-k2 --trust-remote-code --data-parallel-size 16 --data-parallel-size-local 8 --data-parallel-address $MASTER_IP --data-parallel-rpc-port $PORT --enable-expert-parallel --max-num-batched-tokens 8192 --max-num-seqs 256 --gpu-memory-utilization 0.85 --enable-auto-tool-choice --tool-call-parser kimi_k2
-```
-
-## SGLang Deployment
-
-Similarly, we can use TP or DP+EP in SGLang for Deployment, here are the examples.
-
-
-### Tensor Parallelism
-
-Here is the simple example code to run TP16 with two nodes on H200:
-
-``` bash
-# Node 0
-python -m sglang.launch_server --model-path $MODEL_PATH --tp 16 --dist-init-addr $MASTER_IP:50000 --nnodes 2 --node-rank 0 --trust-remote-code --tool-call-parser kimi_k2
-
-# Node 1
-python -m sglang.launch_server --model-path $MODEL_PATH --tp 16 --dist-init-addr $MASTER_IP:50000 --nnodes 2 --node-rank 1 --trust-remote-code --tool-call-parser kimi_k2
-```
-
-**Key parameter notes:**
-- `--tool-call-parser kimi_k2`: Required when enabling tool usage.
-
-### Data Parallelism + Expert Parallelism
-
-Here is an example for large scale Prefill-Decode Disaggregation (4P12D H200) with DP+EP in SGLang:
-
-``` bash
-# for prefill node
-MC_TE_METRIC=true SGLANG_DISAGGREGATION_HEARTBEAT_INTERVAL=10000000 SGLANG_DISAGGREGATION_BOOTSTRAP_TIMEOUT=100000 SGLANG_DISAGGREGATION_WAITING_TIMEOUT=100000 PYTHONUNBUFFERED=1 \
-python -m sglang.launch_server --model-path $MODEL_PATH \
---trust-remote-code --disaggregation-mode prefill --dist-init-addr $PREFILL_NODE0$:5757 --tp-size 32 --dp-size 32 --enable-dp-attention --host $LOCAL_IP --decode-log-interval 1 --disable-radix-cache --enable-deepep-moe --moe-dense-tp-size 1 --enable-dp-lm-head --disable-shared-experts-fusion --watchdog-timeout 1000000 --enable-two-batch-overlap --disaggregation-ib-device $IB_DEVICE --chunked-prefill-size 131072 --mem-fraction-static 0.85 --deepep-mode normal --ep-dispatch-algorithm dynamic --eplb-algorithm deepseek --max-running-requests 1024 --nnodes 4 --node-rank $RANK --tool-call-parser kimi_k2
-
-
-# for decode node
-SGLANG_DEEPEP_NUM_MAX_DISPATCH_TOKENS_PER_RANK=480 MC_TE_METRIC=true SGLANG_DISAGGREGATION_HEARTBEAT_INTERVAL=10000000 SGLANG_DISAGGREGATION_BOOTSTRAP_TIMEOUT=100000 SGLANG_DISAGGREGATION_WAITING_TIMEOUT=100000 PYTHONUNBUFFERED=1 \
-python -m sglang.launch_server --model-path $MODEL_PATH --trust-remote-code --disaggregation-mode decode --dist-init-addr $DECODE_NODE0:5757 --tp-size 96 --dp-size 96 --enable-dp-attention --host $LOCAL_IP --decode-log-interval 1 --context-length 2176 --disable-radix-cache --enable-deepep-moe --moe-dense-tp-size 1 --enable-dp-lm-head --disable-shared-experts-fusion --watchdog-timeout 1000000 --enable-two-batch-overlap --disaggregation-ib-device $IB_DEVICE  --deepep-mode low_latency --mem-fraction-static 0.8 --cuda-graph-bs 480 --max-running-requests 46080 --ep-num-redundant-experts 96 --nnodes 12 --node-rank $RANK --tool-call-parser kimi_k2
-
-# pdlb
-PYTHONUNBUFFERED=1 python -m sglang.srt.disaggregation.launch_lb --prefill http://${PREFILL_NODE0}:30000 --decode http://${DECODE_NODE0}:30000
-```
-
-## KTransformers Deployment
-
-Please copy all configuration files (i.e., everything except the .safetensors files) into the GGUF checkpoint folder at /path/to/K2. Then run:
-``` bash
-python ktransformers/server/main.py  --model_path /path/to/K2 --gguf_path /path/to/K2 --cache_lens 30000
-```
-
-To enable AMX optimization, run:
-
-``` bash
-python ktransformers/server/main.py  --model_path /path/to/K2 --gguf_path /path/to/K2 --cache_lens 30000 --optimize_config_path ktransformers/optimize/optimize_rules/DeepSeek-V3-Chat-fp8-linear-ggml-experts-serve-amx.yaml
-```
-
-## TensorRT-LLM Deployment
-### Prerequisite
-Please refer to [this guide](https://nvidia.github.io/TensorRT-LLM/installation/build-from-source-linux.html) to build TensorRT-LLM v1.0.0-rc2 from source and start a TRT-LLM docker container.
-
-install blobfile by:
-```bash
-pip install blobfile
-```
-### Multi-node Serving
-TensorRT-LLM supports multi-node inference. You can use mpirun to launch Kimi-K2 with multi-node jobs. We will use two nodes for this example.
-
-#### mpirun
-mpirun requires each node to have passwordless ssh access to the other node. We need to setup the environment inside the docker container. Run the container with host network and mount the current directory as well as model directory to the container.
-
-```bash
-# use host network
-IMAGE=<YOUR_IMAGE>
-NAME=test_2node_docker
-# host1
-docker run -it --name ${NAME}_host1 --ipc=host --gpus=all --network host --privileged --ulimit memlock=-1 --ulimit stack=67108864 -v ${PWD}:/workspace -v <YOUR_MODEL_DIR>:/models/DeepSeek-V3 -w /workspace ${IMAGE}
-# host2
-docker run -it --name ${NAME}_host2 --ipc=host --gpus=all --network host --privileged --ulimit memlock=-1 --ulimit stack=67108864 -v ${PWD}:/workspace -v <YOUR_MODEL_DIR>:/models/DeepSeek-V3 -w /workspace ${IMAGE}
-```
-
-Set up ssh inside the container
-
-```bash
-apt-get update && apt-get install -y openssh-server
-
-# modify /etc/ssh/sshd_config
-PermitRootLogin yes
-PubkeyAuthentication yes
-# modify /etc/ssh/sshd_config, change default port 22 to another unused port
-port 2233
-
-# modify /etc/ssh
-```
-
-Generate ssh key on host1 and copy to host2, vice versa.
-
-```bash
-# on host1
-ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519
-ssh-copy-id -i ~/.ssh/id_ed25519.pub root@<HOST2>
-# on host2
-ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519
-ssh-copy-id -i ~/.ssh/id_ed25519.pub root@<HOST1>
-
-# restart ssh service on host1 and host2
-service ssh restart # or
-/etc/init.d/ssh restart # or
-systemctl restart ssh
-```
-
-Generate additional config for trtllm serve.
-```bash
-cat >/path/to/TensorRT-LLM/extra-llm-api-config.yml <<EOF
-cuda_graph_config:
-  padding_enabled: true
-  batch_sizes:
-    - 1
-    - 2
-    - 4
-    - 8
-    - 16
-    - 32
-    - 64
-    - 128
-print_iter_log: true
-enable_attention_dp: true
-EOF
-```
-
-
-After the preparations,you can run the trtllm-serve on two nodes using mpirun:
-
-```bash
-mpirun -np 16 \
--H <HOST1>:8,<HOST2>:8 \
--mca plm_rsh_args "-p 2233" \
---allow-run-as-root \
-trtllm-llmapi-launch trtllm-serve serve \
---backend pytorch \
---tp_size 16 \
---ep_size 8 \
---kv_cache_free_gpu_memory_fraction 0.95 \
---trust_remote_code \
---max_batch_size 128 \
---max_num_tokens 4096 \
---extra_llm_api_options /path/to/TensorRT-LLM/extra-llm-api-config.yml \
---port 8000 \
-<YOUR_MODEL_DIR>
-```
-
-## Others
-
-Kimi-K2 reuses the `DeepSeekV3CausalLM` architecture and convert it's weight into proper shape to save redevelopment effort. To let inference engines distinguish it from DeepSeek-V3 and apply the best optimizations, we set `"model_type": "kimi_k2"` in `config.json`.
-
-If you are using a framework that is not on the recommended list, you can still run the model by manually changing `model_type` to "deepseek_v3" in `config.json` as a temporary workaround. You may need to manually parse tool calls in case no tool call parser is available in your framework.