Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
JIRAIDAUTHSBX-85986
REV5UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c752002f, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c752002f, userName='null'}

This feature provides support for leveraging Graphics Processing Units (GPUs) for increasing transcoding capacity of SBC SWe instances, and the ability to instantiate the same on an OpenStack cloud. GPU acceleration significantly increases transcoding capacity of virtual instances, which otherwise would have a limited scale. In many cases GPU-accelerated solution perform 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 the increased industry investment 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 Page
G.722_Silence_Suppression_Note
G.722_Silence_Suppression_Note

Supported Deployment Scenarios

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

GPU devices are attached to SBC cloud 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 described in Configuring SBC SWe Cloud for GPU Transcoding. For performance considerations, NUMA locality of devices should be ensured.

 

NVIDIA GRID is not supported.

Supported GPU Device

NVIDIA V100(PCIe), 16 GB variant only

Supported Codecs

  • AMR-NB
  • G729
  • G722
  • AMR-WB

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 codec modes and packetization times for the supported codecs are the same as those that apply to SBC SWe in the tables on the Audio Codecs page.

Include Page
GPU_T-SBC_Codec_Restriction
GPU_T-SBC_Codec_Restriction

Feature Comparison of CPU and GPU T-SBC Solutions

While GPU-based T-SBCs 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. 

 

Caption
0Figure
1Feature comparison of CPU and GPU T-SBC solution
Feature
CPU Solution
GPU Solution
ProvisioningCodecs are not provisioned during instantiation.

Codecs and their relative percentages need to be provisioned during instantiation through fields in heat template.

In-band Tone DetectionYesYes (except in a G722 - AMR-WB transcoding scenario)
RFC2833YesYes
Fax Tone DetectionYesNo
LRBT(TPAD)YesNo
G711 Silence SupressionYesYes
 

Pagebreak