Article 5GYFN YouTube is now building its own video-transcoding chips

YouTube is now building its own video-transcoding chips

by
Ron Amadeo
from Ars Technica - All content on (#5GYFN)
24-800x450.jpg

Enlarge / A Google Argos VCU. It transcodes video very quickly. (credit: Google)

Google has decided that YouTube demands such a huge transcoding workload that it needs to build its own server chips. The company detailed its new "Argos" chips in a YouTube blog post, a CNET interview, and in a paper for ASPLOS, the Architectural Support for Programming Languages and Operating Systems Conference. Just as there are GPUs for graphics workloads and Google's TPU (tensor processing unit) for AI workloads, the YouTube infrastructure team says it has created the "VCU" or "Video (trans)Coding Unit," which helps YouTube transcode a single video into over a dozen versions that it needs to provide a smooth, bandwidth-efficient, profitable video site.

Google's Jeff Calow said the Argos chip has brought "up to 20-33x improvements in compute efficiency compared to our previous optimized system, which was running software on traditional servers." The VCU package is a full-length PCI-E card and looks a lot like a graphics card. A board has two Argos ASIC chips buried under a gigantic, passively cooled aluminum heat sink. There's even what looks like an 8-pin power connector on the end because PCI-E just isn't enough power.

Google provided a lovely chip diagram that lists 10 "encoder cores" on each chip, with Google's white paper adding that "all other elements are off-the-shelf IP blocks." Google says that "each encoder core can encode 2160p in realtime, up to 60 FPS (frames per second) using three reference frames."

Read 10 remaining paragraphs | Comments

index?i=c3HUiGod6p8:EU1j0osTuGI:V_sGLiPB index?i=c3HUiGod6p8:EU1j0osTuGI:F7zBnMyn index?d=qj6IDK7rITs index?d=yIl2AUoC8zA
External Content
Source RSS or Atom Feed
Feed Location http://feeds.arstechnica.com/arstechnica/index
Feed Title Ars Technica - All content
Feed Link https://arstechnica.com/
Reply 0 comments