Advanced Usage
This section provides a detailed breakdown of the inferencing script for more advanced users.
Background Noise Removal NIM uses gRPC endpoints. Import the compiled gRPC protos for invoking the NIM.
The NIM invocation uses bi-directional gRPC streaming. To generate the request data stream, define a Python generator function. This is also known as a Python iterator of form, a simple function that yields after a call. The yield returns a chunk to be streamed.
For NIM in streaming mode, the audio_stream_data in a request should be PCM 32-bit float audio data, with each data chunk of size 10 milliseconds for any BNR model.
Before invoking the NIM, define a function that handles the incoming stream and writes it to an output file.
For NIM in streaming mode, the output audio_stream_data in the response is PCM 32-bit float audio data of the same length as the input or request.
Now that we have the request generator and output iterator set up, connect to the NIM and invoke it.
The input file path is stored in the variable input_filepath, and the output file is written to the location specified in the variable output_filepath.
Wait for a message confirming that the function invocation has completed before checking the output file.
Fill in the correct host and port for your target in the following code snippet:
Compile the Protos (Optional)
The NVIDIA Maxine NIM Clients package comes with the pre-compiled protos. However, to compile the protos locally, install the required dependencies.
With the compilation script, you can generate compiled protos that match your specific programming language (such as Python or C++) and version requirements, ensuring compatibility between client applications and compiled protos in your custom implementations.
Linux
To compile protos on Linux, run:
Windows
To compile protos on Windows, run:
Model Caching
When the container starts for the first time, it downloads the required models from NGC. To avoid downloading the models on subsequent runs, you can cache them locally by using a cache directory:
Ensure the nim_model_profile is compatible with your GPU. For more information about nim_model_profile, refer to the NIM Model Profile Table.
Multiple Concurrent Inputs
To run the server in multi-input concurrent mode, set the environment variable MAXINE_MAX_CONCURRENCY_PER_GPU to an integer greater than 1 in the server container. The server will then accept as many concurrent inputs per GPU as specified by the MAXINE_MAX_CONCURRENCY_PER_GPU variable.
Because Triton distributes the workload equally across all GPUs, if the count of GPUs equals NUM_GPUS, the total number of concurrent inputs supported by the server is NUM_GPUS * MAXINE_MAX_CONCURRENCY_PER_GPU.
The number of concurrent streams supported by the NIM vary with the amount of resources available on the system, including CPUs, system memory, and GPU VRAM. If the system does not have enough resources to load the server, server launch will fail with error logs similar to the following:
OpenBLAS blas_thread_init: pthread_create failed for thread 14 of 16: Resource temporarily unavailable
If such an error is encountered, reduce the number of streams (MAXINE_MAX_CONCURRENCY_PER_GPU) when launching the container.