Page History

This feature provides support for leveraging The SBC can leverage Graphics Processing Units (GPUs) for increasing increased transcoding capacity of T-SBC SWe instances, and the ability to instantiate the same on an OpenStack cloudinstances deployed in OpenStack cloud environments (Newton and above). GPU acceleration significantly increases transcoding capacity of virtual instances, which otherwise would have a limited scale. In many cases a GPU-accelerated solution performs better than specialized DSP hardware-based solutions. GPU-based solutions have the following benefits:

• GPUs are ubiquitous, they are being offered as Commercial Off-the-Shelf (COTS) solutions by major hardware and cloud vendors.
• GPU-based solutions help leverage the steep rise in computing power delivered by increased industry investments in GPU technology.
• GPUs have diverse applications. Unlike specialized DSP hardware, GPU devices can be reused for other applications.
• GPUs can be leveraged by cloud-based virtual instances.

Include PageG

• .

722_Silence_Suppression_Note

G.722_Silence_Suppression_Note

GPU Transcoding

Prior to SBC 8.0 release, for GPU-based solutions, the 

Spacevars
0 product

could not offer more than one transcodable codec in the outgoing offer for following reasons:

• Unlike CPU-based DSP that supports all the codecs, the GPU-based DSP supports specific codecs.
• For GPU, if the configured codecs do not reside on the same DSP process, they cannot be used with a single DSP allocation.
• Unaware of the cluster capabilities, the signaling SBC removes the codecs from the outgoing offer, which cannot be supported by the reserved DSP.

 

The

Spacevars
0 product

 is enhanced to offer all the configured transcodable codecs that the 

Spacevars
0 product

supports, in the outgoing offer and address the above GPU gaps.

The configured codecs include:

• Codecs configured for transcoding
• Codecs supported by same T-SBC instance that supports codecs received in the offer.

Supported Deployment Scenarios

GPU acceleration is currently supported on SBC SWe cloud-based TT-SBC instances and I-SBC instances, on OpenStack (Newton and above). The T-SBC is a component in Distributed SBC architecture that provides transcoding service.

It is also on I-SBC. 

GPU devices are attached to the SBC cloud SWe instances through PCIe pass-through – a single GPU device can be used by only one instance at a time. The process of enabling PCIe pass-through in OpenStack is detailed later in this document. For performance considerations, NUMA locality of devices should be ensured.

Supported GPU Devices

The following NVIDIA GPU devices are supported.

NVIDIA V100(PCIe)

Supported Codecs

• AMR-NB
• G729G.729AB
• G722
• AMR-WB
• EVRC
• EVRCB

In addition, G.711 is supported for GPU instances, but only when G.711 is being transcoded to a non-G.711 codec. You cannot currently configure transcoding from G.711 to G.711 on GPU instances. The coding rates and packetization times for the supported codecs are shown in the tables on the Audio Codecs page.

Include Page
GPU_T-SBC_Codec_Restriction GPU_T-SBC_Codec_Restriction

Caption
0 Table 1 Feature Differences between CPU and GPU
Feature CPU GPU Native Frame Size (for Encoder) 10ms 20ms Packetization Times Supported 10ms, 20ms, 30ms, 40ms, 50ms, 60ms 20ms, 40ms and 60ms

Feature Comparison of CPU and GPU T-SBC Solutions

While GPU-based T-SBCs SBC SWes offer marked increase in scale when compared to CPU-based T-SBCs, there are some caveats with the GPU solution that are highlighted in the following table. 

Pagebreak