# TensorRT-LLM Integration with Triton Distributed This example demonstrates how to use Triton Distributed to serve large language models with the tensorrt_llm engine, enabling efficient model serving with both monolithic and disaggregated deployment options. ## Prerequisites Start required services (etcd and NATS): Option A: Using [Docker Compose](/runtime/rust/docker-compose.yml) (Recommended) ```bash docker-compose up -d ``` Option B: Manual Setup - [NATS.io](https://docs.nats.io/running-a-nats-service/introduction/installation) server with [Jetstream](https://docs.nats.io/nats-concepts/jetstream) - example: `nats-server -js --trace` - [etcd](https://etcd.io) server - follow instructions in [etcd installation](https://etcd.io/docs/v3.5/install/) to start an `etcd-server` locally - example: `etcd --listen-client-urls http://0.0.0.0:2379 --advertise-client-urls http://0.0.0.0:2379` ## Building the Environment TODO: Remove the internal references below. - Build TRT-LLM wheel using latest tensorrt_llm main ``` git clone https://github.com/NVIDIA/TensorRT-LLM.git cd TensorRT-LLM # Start a dev docker container. Dont forget to mount your home directory to /home in the docker run command. make -C docker jenkins_run LOCAL_USER=1 DOCKER_RUN_ARGS="-v /user/home:/home" # Build wheel for the GPU architecture you are currently using ("native"). # We use -f to run fast build which should speed up the build process. But it might not work for all GPUs and for full functionality you should disable it. python3 scripts/build_wheel.py --clean --trt_root /usr/local/tensorrt -a native -i -p -ccache # Copy wheel to your local directory cp build/tensorrt_llm-*.whl /home ``` - Build the Triton Distributed container ```bash # Build image ./container/build.sh --base-image gitlab-master.nvidia.com:5005/dl/dgx/tritonserver/tensorrt-llm/amd64 --base-image-tag krish-fix-trtllm-build.23766174 ``` Alternatively, you can build with latest tensorrt_llm pipeline like below: ```bash # Build image ./container/build.sh --framework TENSORRTLLM --skip-clone-tensorrtllm 1 --base-image urm.nvidia.com/sw-tensorrt-docker/tensorrt-llm-staging/release --base-image-tag main ``` **Note:** If you are using the latest tensorrt_llm image, you do not need to install the TRT-LLM wheel. ## Launching the Environment ``` # Run image interactively from with the triton distributed root directory. ./container/run.sh --framework TENSORRTLLM -it -v /home/:/home/ # Install the TRT-LLM wheel. No need to do this if you are using the latest tensorrt_llm image. pip install /home/tensorrt_llm-*.whl ``` ## Deployment Options Note: NATS and ETCD servers should be running and accessible from the container as described in the [Prerequisites](#prerequisites) section. ### 1. Monolithic Deployment Run the server and client components in separate terminal sessions: **Server:** Note: The following commands are tested on machines withH100x8 GPUs #### Option 1.1 Single-Node Single-GPU ```bash # Launch worker cd /workspace/examples/python_rs/llm/tensorrt_llm mpirun --allow-run-as-root -n 1 --oversubscribe python3 -m monolith.worker --engine_args model.json ``` Upon successful launch, the output should look similar to: ```bash [TensorRT-LLM][INFO] KV cache block reuse is disabled [TensorRT-LLM][INFO] Max KV cache pages per sequence: 2048 [TensorRT-LLM][INFO] Number of tokens per block: 64. [TensorRT-LLM][INFO] [MemUsageChange] Allocated 26.91 GiB for max tokens in paged KV cache (220480). [02/14/2025-09:38:53] [TRT-LLM] [I] max_seq_len=131072, max_num_requests=2048, max_num_tokens=8192 [02/14/2025-09:38:53] [TRT-LLM] [I] Engine loaded and ready to serve... ``` `nvidia-smi` can be used to check the GPU usage and the model is loaded on single GPU. #### Option 1.2 Single-Node Multi-GPU Update `tensor_parallel_size` in the `model.json` to load the model with the desired number of GPUs. For this example, we will load the model with 4 GPUs. ```bash # Launch worker cd /workspace/examples/python_rs/llm/tensorrt_llm mpirun --allow-run-as-root -n 1 --oversubscribe python3 -m monolith.worker --engine_args model.json ``` `nvidia-smi` can be used to check the GPU usage and the model is loaded on 4 GPUs. #### Option 1.3 Multi-Node Multi-GPU Tanmay[WIP] **Client:** ```bash # Run client python3 -m common.client \ --prompt "Describe the capital of France" \ --max-tokens 10 \ --temperature 0.5 \ --component tensorrt-llm ``` The output should look similar to: ``` Annotated(data=',', event=None, comment=[], id=None) Annotated(data=', Paris', event=None, comment=[], id=None) Annotated(data=', Paris,', event=None, comment=[], id=None) Annotated(data=', Paris, in', event=None, comment=[], id=None) Annotated(data=', Paris, in terms', event=None, comment=[], id=None) Annotated(data=', Paris, in terms of', event=None, comment=[], id=None) Annotated(data=', Paris, in terms of its', event=None, comment=[], id=None) Annotated(data=', Paris, in terms of its history', event=None, comment=[], id=None) Annotated(data=', Paris, in terms of its history,', event=None, comment=[], id=None) Annotated(data=', Paris, in terms of its history, culture', event=None, comment=[], id=None) ``` ### 2. Disaggregated Deployment #### 2.1 Single-Node Disaggregated Deployment **Environment** This is the latest image with tensorrt_llm supporting distributed serving with pytorch workflow in LLM API. Run the container interactively with the following command: ```bash ./container/run.sh --image IMAGE -it ``` **TRTLLM LLMAPI Disaggregated config file** Define disaggregated config file similar to the example [single_node_config.yaml](disaggregated/llmapi_disaggregated_configs/single_node_config.yaml). The important sections are the model, context_servers and generation_servers. **Launch the servers** Launch context and generation servers.\ WORLD_SIZE is the total number of workers covering all the servers described in disaggregated configuration.\ For example, 2 TP2 generation servers are 2 servers but 4 workers/mpi executor. ```bash cd /workspace/examples/python_rs/llm/tensorrt_llm/ mpirun --allow-run-as-root --oversubscribe -n WORLD_SIZE python3 -m disaggregated.worker --engine_args model.json -c disaggregated/llmapi_disaggregated_configs/single_node_config.yaml & ``` If using the provided [single_node_config.yaml](disaggregated/llmapi_disaggregated_configs/single_node_config.yaml), WORLD_SIZE should be 3 as it has 2 context servers(TP=1) and 1 generation server(TP=1). **Launch the router** ```bash cd /workspace/examples/python_rs/llm/tensorrt_llm/ python3 -m disaggregated.router -c disaggregated/llmapi_disaggregated_configs/single_node_config.yaml & ``` **Send Requests** ```bash cd /workspace/examples/python_rs/llm/tensorrt_llm/ python3 -m common.client \ --prompt "Describe the capital of France" \ --max-tokens 10 \ --temperature 0.5 \ --component router ``` For more details on the disaggregated deployment, please refer to the [TRT-LLM example](#TODO). ### 3. Multi-Node Disaggregated Deployment To run the disaggregated deployment across multiple nodes, we need to launch the servers using MPI, pass the correct NATS and etcd endpoints to each server and update the LLMAPI disaggregated config file to use the correct endpoints. 1. Allocate nodes The following command allocates nodes for the job and returns the allocated nodes. ```bash salloc -A ACCOUNT -N NUM_NODES -p batch -J JOB_NAME -t HH:MM:SS ``` You can use `squeue -u $USER` to check the URLs of the allocated nodes. These URLs should be added to the TRTLLM LLMAPI disaggregated config file as shown below. ```yaml model: TinyLlama/TinyLlama-1.1B-Chat-v1.0 ... context_servers: num_instances: 2 gpu_fraction: 0.25 tp_size: 2 pp_size: 1 urls: - "node1:8001" - "node2:8002" generation_servers: num_instances: 2 gpu_fraction: 0.25 tp_size: 2 pp_size: 1 urls: - "node2:8003" - "node2:8004" ``` 2. Start the NATS and ETCD endpoints Use the following commands. These commands will require downloading [NATS.io](https://docs.nats.io/running-a-nats-service/introduction/installation) and [ETCD](https://etcd.io/docs/v3.5/install/): ```bash ./nats-server -js --trace ./etcd --listen-client-urls http://0.0.0.0:2379 --advertise-client-urls http://0.0.0.0:2379 ``` Export the correct NATS and etcd endpoints. ```bash export NATS_SERVER="nats://node1:4222" export ETCD_ENDPOINTS="http://node1:2379,http://node2:2379" ``` 3. Launch the workers from node1 or login node. WORLD_SIZE is similar to single node deployment. Update the `model.json` to point to the new disagg config file. ```bash srun --mpi pmix -N NUM_NODES --ntasks WORLD_SIZE --ntasks-per-node=WORLD_SIZE --no-container-mount-home --overlap --container-image IMAGE --output batch_%x_%j.log --err batch_%x_%j.err --container-mounts PATH_TO_TRITON_DISTRIBUTED:/workspace --container-env=NATS_SERVER,ETCD_ENDPOINTS bash -c 'cd /workspace/examples/python_rs/llm/tensorrt_llm && python3 -m disaggregated.worker --engine_args model.json -c disaggregated/llmapi_disaggregated_configs/multi_node_config.yaml' & ``` Once the workers are launched, you should see the output similar to the following in the worker logs. ``` [TensorRT-LLM][INFO] [MemUsageChange] Allocated 18.88 GiB for max tokens in paged KV cache (1800032). [02/20/2025-07:10:33] [TRT-LLM] [I] max_seq_len=2048, max_num_requests=2048, max_num_tokens=8192 [02/20/2025-07:10:33] [TRT-LLM] [I] Engine loaded and ready to serve... [02/20/2025-07:10:33] [TRT-LLM] [I] max_seq_len=2048, max_num_requests=2048, max_num_tokens=8192 [TensorRT-LLM][INFO] Number of tokens per block: 32. [TensorRT-LLM][INFO] [MemUsageChange] Allocated 18.88 GiB for max tokens in paged KV cache (1800032). [02/20/2025-07:10:33] [TRT-LLM] [I] max_seq_len=2048, max_num_requests=2048, max_num_tokens=8192 [02/20/2025-07:10:33] [TRT-LLM] [I] Engine loaded and ready to serve... ``` 4. Launch the router from node1 or login node. ```bash srun --mpi pmix -N 1 --ntasks 1 --ntasks-per-node=1 --overlap --container-image IMAGE --output batch_router_%x_%j.log --err batch_router_%x_%j.err --container-mounts PATH_TO_TRITON_DISTRIBUTED:/workspace --container-env=NATS_SERVER,ETCD_ENDPOINTS bash -c 'cd /workspace/examples/python_rs/llm/tensorrt_llm && python3 -m disaggregated.router -c disaggregated/llmapi_disaggregated_configs/multi_node_config.yaml' & ``` 5. Send requests to the router. ```bash srun --mpi pmix -N 1 --ntasks 1 --ntasks-per-node=1 --overlap --container-image IMAGE --output batch_client_%x_%j.log --err batch_client_%x_%j.err --container-mounts PATH_TO_TRITON_DISTRIBUTED:/workspace --container-env=NATS_SERVER,ETCD_ENDPOINTS bash -c 'cd /workspace/examples/python_rs/llm/tensorrt_llm && python3 -m common.client --prompt "Describe the capital of France" --max-tokens 10 --temperature 0.5 --component router' & ``` Finally, you should see the output similar to the following in the client logs. ``` Annotated(data='and', event=None, comment=[], id=None) Annotated(data='and its', event=None, comment=[], id=None) Annotated(data='and its significance', event=None, comment=[], id=None) Annotated(data='and its significance in', event=None, comment=[], id=None) Annotated(data='and its significance in the', event=None, comment=[], id=None) Annotated(data='and its significance in the country', event=None, comment=[], id=None) Annotated(data="and its significance in the country'", event=None, comment=[], id=None) Annotated(data="and its significance in the country's", event=None, comment=[], id=None) Annotated(data="and its significance in the country's history", event=None, comment=[], id=None) Annotated(data="and its significance in the country's history.", event=None, comment=[], id=None) ```