FAQ#
What are the advantages of running a model with Triton Inference Server compared to running directly using the model’s framework API?#
When using Triton Inference Server the inference result will be the same as when using the model’s framework directly. However, with Triton you get benefits like concurrent model execution (the ability to run multiple models at the same time on the same GPU) and dynamic batching to get better throughput. You can also replace or upgrade models while Triton and client application are running. Another benefit is that Triton can be deployed as a Docker container, anywhere – on premises and on public clouds. Triton Inference Server also supports multiple frameworks such as TensorRT, TensorFlow, PyTorch, and ONNX on both GPUs and CPUs leading to a streamlined deployment.
Can Triton Inference Server run on systems that don’t have GPUs?#
Yes, the QuickStart guide describes how to run Triton on a CPU-Only System.
Can Triton Inference Server be used in non-Docker environments?#
Yes. Triton Inference Server can also be built from source on your “bare metal” system.
Do you provide client libraries for languages other than C++ and Python?#
We provide C++ and Python client libraries to make it easy for users to write client applications that communicate with Triton. We chose those languages because they were likely to be popular and performant in the ML inference space, but in the future we can possibly add other languages if there is a need.
We provide the GRPC API as a way to generate your own client library for a large number of languages. By following the official GRPC documentation and using grpc_service.proto you can generate language bindings for all the languages supported by GRPC. We provide three examples of this for Go, Python and Java.
In general the client libraries (and client examples) are meant to be just that, examples. We feel the client libraries are well written and well tested, but they are not meant to serve every possible use case. In some cases you may want to develop your own customized library to suit your specific needs.
How would you use Triton Inference Server within the AWS environment?#
In an AWS environment, the Triton Inference Server docker container can run on CPU-only instances or GPU compute instances. Triton can run directly on the compute instance or inside Elastic Kubernetes Service (EKS). In addition, other AWS services such as Elastic Load Balancer (ELB) can be used for load balancing traffic among multiple Triton instances. Elastic Block Store (EBS) or S3 can be used for storing deep-learning models loaded by the inference server.
How do I measure the performance of my model running in the Triton Inference Server?#
The Triton Inference Server exposes performance information in two ways: by Prometheus metrics and by the statistics available through the HTTP/REST, GRPC, and C APIs.
A client application, perf_analyzer, allows you to measure the performance of an individual model using a synthetic load. The perf_analyzer application is designed to show you the tradeoff of latency vs. throughput.
How can I fully utilize the GPU with Triton Inference Server?#
Triton Inference Server has several features designed to increase GPU utilization:
Triton can simultaneously perform inference for multiple models (using either the same or different frameworks) using the same GPU.
Triton can increase inference throughput by using multiple instances of the same model to handle multiple simultaneous inferences requests to that model. Triton chooses reasonable defaults but you can also control the exact level of concurrency on a model-by-model basis.
Triton can batch together multiple inference requests into a single inference execution. Typically, batching inference requests leads to much higher thoughput with only a relatively small increase in latency.
As a general rule, batching is the most beneficial way to increase GPU utilization. So you should always try enabling the dynamic batcher with your models. Using multiple instances of a model can also provide some benefit but is typically most useful for models that have small compute requirements. Most models will benefit from using two instances but more than that is often not useful.
If I have a server with multiple GPUs should I use one Triton Inference Server to manage all GPUs or should I use multiple inference servers, one for each GPU?#
Triton Inference Server will take advantage of all GPUs that it has access to on the server. You can limit the GPUs available to Triton by using the CUDA_VISIBLE_DEVICES environment variable (or with Docker you can also use NVIDIA_VISIBLE_DEVICES or –gpus flag when launching the container). When using multiple GPUs, Triton will distribute inference request across the GPUs to keep them all equally utilized. You can also control more explicitly which models are running on which GPUs.
In some deployment and orchestration environments (for example, Kubernetes) it may be more desirable to partition a single multi-GPU server into multiple nodes, each with one GPU. In this case the orchestration environment will run a different Triton for each GPU and an load balancer will be used to divide inference requests across the available Triton instances.
If the server segfaults, how can I debug it?#
The NGC build is a Release build and does not contain Debug symbols. The build.py as well defaults to a Release build. Refer to the instructions in build.md to create a Debug build of Triton. This will help find the cause of the segmentation fault when looking at the gdb trace for the segfault.
When opening a GitHub issue for the segfault with Triton, please include the backtrace to better help us resolve the problem.
What are the benefits of using Triton Inference Server as part of the NVIDIA AI Enterprise Software Suite?#
NVIDIA AI Enterprise enables enterprises to implement full AI workflows by delivering an entire end-to-end AI platform. Four key benefits:
Enterprise-Grade Support, Security & API Stability:#
Business-critical AI projects stay on track with NVIDIA Enterprise Support, available globally to assist both IT teams with deploying and managing the lifecycle of AI applications and the developer teams with building AI applications. Support includes maintenance updates, dependable SLAs and response times. Regular security reviews and priority notifications mitigate potential risk of unmanaged opensource and ensure compliance with corporate standards. Finally, long term support and regression testing ensures API stability between releases.
Speed time to production with AI Workflows & Pretrained Models:#
To reduce the complexity of developing common AI applications, NVIDIA AI Enterprise includes AI workflows which are reference applications for specific business outcomes such as Intelligent Virtual Assistants and Digital Fingerprinting for real-time cybersecurity threat detection. AI workflow reference applications may include AI frameworks and pretrained models, Helm Charts, Jupyter Notebooks and documentation.
Performance for Efficiency and Cost Savings:#
Using accelerated compute for AI workloads such as data process with NVIDIA RAPIDS Accelerator for Apache Spark and inference with Triton Inference Sever delivers better performance which also improves efficiency and reduces operation and infrastructure costs, including savings from reduced time and energy consumption.
Optimized and Certified to Deploy Everywhere:#
Cloud, Data Center, Edge Optimized and certified to ensure reliable performance whether it’s running your AI in the public cloud, virtualized data centers, or on DGX systems.