Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH2AUTH1REV5REV6REV3REV1
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
JIRAIDAUTHSBX-102120
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c752002f, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb1e054d, userName='null'}

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.


GPU Transcoding

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

Spacevars
0product
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
0product
 is enhanced to offer all the configured transcodable codecs that the 
Spacevars
0product
supports, in the outgoing offer and address the above GPU gaps.

The configured codecs includeG.722_Silence_Suppression_NoteG.722_Silence_Suppression_Note:

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

 

NVIDIA GRID is not supported.

Supported GPU Devices

The following NVIDIA GPU devices are supported.

GPU Device NamePCI Vendor IDPCI Device
NVIDIA V100(PCIe)
IDReleases supportedRemarks
Tesla V100 PCIe 16GB10DE1DB47.0.0 onwardsrecommended
Tesla V100 SXM2 16GB10DE1DB17.2.0 onwards

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
0Table
1Feature 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. 


 
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

are provisioned during instantiation

through

using fields in

heat

the Heat template.

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


 



Pagebreak