Skip to content

Latest commit

 

History

History
43 lines (28 loc) · 3.79 KB

HW_Video_Acceleration_in_Chrom{eium}{OS}.md

File metadata and controls

43 lines (28 loc) · 3.79 KB

HW Video Acceleration in Chrom{e,ium}{,OS}

Ami Fischman [email protected]

Status as of 2014/06/06: Up-to-date

(could use some more details)

Introduction

Video decode (e.g. YouTube playback) and encode (e.g. video chat applications) are some of the most complex compute operations on the modern web. Moving these operations from software running on general-purpose CPUs to dedicated hardware blocks means lower power consumption, longer battery life, higher quality (e.g. HD instead of SD), and better interactive performance as the CPU is freed up to work on everything else it needs to do.

Design

media::VideoDecodeAccelerator (VDA) and media::VideoEncodeAccelerator (VEA) (with their respective Client subclasses) are the interfaces at the center of all video HW acceleration in Chrome. Each consumer of HW acceleration implements the relevant Client interface and calls an object of the relevant V[DE]A interface.

In general the classes that want to encode or decode video live in the renderer process (e.g. the

Implementation Details

The main consumers of the acceleration APIs are:

Current Status

New devices are released all the time so this list is likely already out of date, but as of early June 2014, existing (public) support includes: Decode

  • Windows: starting with Windows 7, HW accelerated decode of h.264 is used via DXVAVDA.
  • CrOS/Intel (everything post-Mario/Alex/ZGB): HW accelerated decode of h.264 is used via VAVDA
  • CrOS/ARM: HW accelerated decode of VP8 and h.264 is available via V4L2VDA
  • Android: HW accelerated decode of VP8 is available on N10, N5, some S4’s, and a bunch of other devices. (note that on Android this only applies to WebRTC, as there is no PPAPI and
  • CrOS/ARM: HW accelerated encode of h.264 (everywhere) and VP8 (2014 devices) is available via V4L2VEA
  • Android: HW accelerated encode of VP8 is available on N5.

Results

Generally speaking offloading encode or decode from CPU to specialized HW has shown an overall battery-life extension of 10-25% depending on the platform, workload, etc. For some data examples see: public: 133827#c27, 219957#c16 google-internal only: summary slide deck, CrOS/ARM-1, CrOS/ARM-2