You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

 

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 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.

Note

G.722 Silence Suppression is not supported with GPU transcoding.

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 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 detailed later in this document. For performance considerations, NUMA locality of devices should be ensured.

 

NVIDIA GRID is not supported.

Supported GPU Device

NVIDIA V100(PCIe)

Supported Codecs

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


Note for Releases Prior to 8.0

The GPU transcoding solution currently does not support more than one non-G711 transcodable codec per leg on a trunk group. Therefore when configuring Packet Service Profiles, do not configure multiple non-G711 codecs on a single leg (This Leg/Other Leg parameters) when specifying the Codecs Allowed For Transcoding within Packet To Packet Control. Refer to Packet Service Profile - CLI or Packet To Packet Control - Codecs Allowed For Transcoding (EMA).

Note for Releases 8.x/9.x

Following issues exist in 8.x/9.x releases:

  • If  the first transcodable codec in the SDP offered by SBC is G.711, and the answer comes for non-G711 codec, then the SBC continues to use CPU resources for non-G711 transcoding.
  • If the first transcodable codec in the SDP offered by SBC is non-G711 and the answer comes for G711, then the SBC continues to use GPU resources for G.711 transcoding.

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. 

 

Feature 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.

Inband tone DetectionYesYes (except in G722 - AMRWB transcoding scenario)
RFC2833YesYes
Fax Tone DetectionYesNo
LRBT(TPAD)YesNo
G711 Silence SupressionYesYes
 

  • No labels