Live Video in a Modern Web Environment
summary
Twitch claims delivery to over 60 million monthly visitors and handles peaks above a million concurrent viewers while ingesting streams over RTMP ingest at 18 global nodes, then transmux to HLS, transcode partners into multiple bitrates, segment into ~4s chunks and push to CDN. Latency components are concrete: ingest <1s, transcoding ~5s, CDN ~1s, plus a two-segment initial buffer (≈8s) yielding typical 10–20s live delay. HLS playback often runs through HLS converted to FLV inside Flash, saving ad features but costing CPU.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:00What is Twitch
- 4:09Desktop Usage
- 6:10Twitch Plays Pokemon
- 7:29Twitch Statistics
- 8:27CSGO Tournament
- 8:46Streaming Platforms
- 18:30Browsers
- 21:50Flash
- 25:11Media Source Extensions
- 28:46Latency
- 31:04Time Travel Latency
- 32:54Chat vs Live Video
- 33:25Conclusion
- 34:55Twitch
- 35:13TwitchCon
- 35:42Questions
- 35:52Is Twitch owned by Amazon
- 37:20Transcoding VODs
- 39:54Testing on Twitch
- 42:04Viewbotting
related talks
19mLow Latency Live from a Different Vantage Point
24mVideo streaming on the web: Live and recorded video streaming
35mLive Low Latency Video Streaming
16mCDN Challenges of HTTP-based Low Latency Live Streaming Delivery
10mMeasuring the live video latency at scale
17mLive Video Streaming as "tail -f"
21mThe challenges of deploying Apple's Low Latency HLS In Real Life
18mHow we accelerated Live 2 VOD delivery from 15 minutes to under a minute