Support Matrix
About Model Profiles
The models for NVIDIA NIM microservices use model engines that are tuned for specific NVIDIA GPU models, number of GPUs, precision, and so on. NVIDIA produces model engines for several popular combinations and these are referred to as model profiles. Each model profile is identified by a unique 64-character string of hexadecimal digits that is referred to as a profile ID.
The NIM microservices support automatic profile selection by determining the GPU model and count on the node and attempting to match the optimal model profile. Alternatively, NIM microservices support running a specified model profile, but this requires that you review the profiles and know the profile ID.
The available model profiles are stored in a file in the NIM container file system.
The file is referred to as the model manifest file and the default path is /opt/nim/etc/default/model_manifest.yaml in the container.
NVIDIA Llama 3.1 NemoGuard 8B TopicGuard Model Profiles
The model requires 48 GB of GPU memory. NVIDIA developed and tested the microservice using H100, A100, and A6000 GPUs. You can use a single GPU with that capacity or two GPUs that meet the capacity.
For information about locally-buildable and generic model profiles, refer to profiles in the NIM for LLMs documentation.
Profiles from the 1.3.0 model manifest
The 1.0.0 documentation snapshot uses a model manifest labeled 1.3.0. The manifest defines five locally buildable profiles and three generic profiles. All use BF16 precision and require 14.97 GB of disk space.
Locally Buildable Model Profiles
Generic Model Profiles
The tensor parallel 4 GPU profiles are not runnable. This is a known issue.