Skip to content

[Question] Can I build the tritonserver, tensorrtllm_backend and tensorrtllm and then use these build files across servers? #2423

Closed as not planned

Description

@chrisreese-if

I want to deploy triton + tensorrtllm, due to some constraints I cannot use docker container. I have figured out that I need to build the following repos:

  1. https://github.com/triton-inference-server/server
  2. https://github.com/NVIDIA/TensorRT
  3. https://github.com/NVIDIA/TensorRT-LLM
  4. https://github.com/triton-inference-server/tensorrtllm_backend

First, am I missing something, or should this give me everything i need to deploy a triton inference server with tensorrt_llm backend? Second, these take a few hours to build so can I build these for a specific linux and CUDA version and use them across servers (all with potentially different GPUs), given that all the servers have the same linux and CUDA version?

Finally when building LLM models using trt_build can I reuse these models across GPUs or if built on H100, they can only be used on H100?

Thank you for all your work!

Activity

  1. added
    questionFurther information is requested
    triagedIssue has been triaged by maintainers
    on Nov 8, 2024
  2. pcastonguay commented on Nov 12, 2024

    @pcastonguay
    Collaborator

    Yes, you should be able to build for a specific linux and CUDA version and use across servers with same linux and CUDA version.

    However, the TRT-LLM engines generated by trtllm-build are optimized for a specific GPU type and cannot be reused across different GPUs.

  3. chrisreese-if commented on Nov 12, 2024

    @chrisreese-if
    Author

    Thank you @pcastonguay for getting back to me. Just to confirm, if I build all of these:
    https://github.com/triton-inference-server/server
    https://github.com/NVIDIA/TensorRT
    https://github.com/NVIDIA/TensorRT-LLM
    https://github.com/triton-inference-server/tensorrtllm_backend

    I should have everything to deploy triton + tensorrt_llm_backend, right? Am I missing some steps?

  4. pcastonguay commented on Nov 12, 2024

    @pcastonguay
    Collaborator

    This should give you everything you need.

  5. chrisreese-if commented on Nov 12, 2024

    @chrisreese-if
    Author

    Great! Thank you.

  6. chrisreese-if commented on Nov 15, 2024

    @chrisreese-if
    Author

    Hey @pcastonguay I have a follow up question:

    Can I take the built files from inside the triton container, and use those? Instead of building it myself? What would that look like, is it even possible?

  7. chrisreese-if commented on Nov 15, 2024

    @chrisreese-if
    Author

    From inside the container, I can see:

    root@__:/# cat /etc/os-release
    PRETTY_NAME="Ubuntu 22.04.4 LTS"
    NAME="Ubuntu"
    VERSION_ID="22.04"
    VERSION="22.04.4 LTS (Jammy Jellyfish)"
    VERSION_CODENAME=jammy
    ID=ubuntu
    ID_LIKE=debian
    HOME_URL="https://www.ubuntu.com/"
    SUPPORT_URL="https://help.ubuntu.com/"
    BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
    PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
    UBUNTU_CODENAME=jammy
    

    So I can use the build files from the container directly, as long as the CUDA version matches, and its Ubuntu 22.04.4, right?

  8. pcastonguay commented on Nov 18, 2024

    @pcastonguay
    Collaborator

    Yes that should work if needed shared libraries versions match too.

  9. chrisreese-if commented on Nov 19, 2024

    @chrisreese-if
    Author

    I tried just using tar to zip the / and recreating it completely (as a best cause scenario), it bugged out because the new server's driver version didn't match exactly. So I am guessing the driver version should exactly match too? @pcastonguay

  10. karljang commented on Dec 1, 2025

    @karljang
    Collaborator

    @chrisreese-if , Just checking in to see if this issue is still relevant for you. If not, please let me know, so I can close it.
    By the way, I think your guess was generally right~ :)

  11. github-actions commented on Dec 16, 2025

    @github-actions

    Issue has not received an update in over 14 days. Adding stale label.

  12. github-actions commented on Dec 31, 2025

    @github-actions

    This issue was closed because it has been 14 days without activity since it has been marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions