Brightcove live tech overview
- 1. Brightcove live Jordi Cenzano | @jordicenzano | jordicenzano Tech overview Director of engineering for live services
- 2. ● Live streaming? ● Brightcove live block diagram ● Ingest ○ Best practices ● Live clipping ● Delivery ○ Best practices ○ FUTURE: In-manifest redundancy ● SSAI ● Monitoring ● Latency ○ R&D: LHLS ● R&D: Edge computing possibilities (improve hit ratio) Agenda
- 4. Live streaming? Is it possible to create a POC of a live streaming platform in 5min?
- 5. Demo simple live streaming -DEMO-
- 6. What is live streaming? RTMP TS (UDP/TCP/RTP FEC?) SRT Zixi HLS ??? # Renditions Bitrates Resolutions Codecs (profiles / levels) TTL? Pre warm? Token auth? Geoblocked? ??? Chrome Firefox Safari (MacOS) IOS Android? Chromecast …. HLS DASH Smooth
- 7. What is live streaming? # Renditions Bitrates Resolutions Codecs (profiles / levels) HLS DASH Smooth TTL? Pre warm? Token auth? Geoblocked? ??? Chrome Firefox Safari (MacOS) IOS Android? Chromecast …. RTMP TS (UDP/TCP/RTP FEC?) SRT Zixi HLS ???
- 9. Ingest
- 10. ● Use job redundancy in different regions ● 10Mbps BW != 10Mbps in RTMP (TCP) ○ Find correct encoding bitrate (*) ● Choose closer region to your encoder (lowest RTT, big impact in TCP throughput) ● Avoid RTMP disconnections ○ Firewalls: Allow persistent TCP ○ Use reliable networks, at least main feed (guaranteed BW if possible) ○ Avoid RTMP “men in the middle” ● Use RTMP log/pass & IP whitelist Ingest: Best practices (*) https://www.switch.ch/network/tools/tcp_throughput/
- 11. Live clipping ● Clipping methods (API based) ○ Last X seconds of the live stream ○ SMPTE Timecode (Recommended) ○ UTC time (set when we receive the data) ○ Offset from start of stream (NOT recommended) ■ Problems on disconnections ○ Credentials: ■ Ftp, AWS, VC, OAuth
- 12. Delivery
- 14. In manifest redundancy #EXTM3U #EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=200000, RESOLUTION=720x480 http://A.CDN.com/480p/index.m3u8 #EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=200000, RESOLUTION=720x480 http://B.CDN.com/480p/index.m3u8 from: https://developer.apple.com/
- 17. NOT targeted (lineal broadcast) Ads Targeted Client side (player) Server side (SSAI)
- 18. Live streaming with SSAI
- 19. ● For 1M CCU and 6s TD ● 333K DB transactions /s (in few ms each) ● 1M Adbreak req / 6s = 166K adreq/s ○ Process ads, tracking events ○ Ingest ads media ■ Res., fps, audio level, bitrate, etc ● For adbreak 6 ads and 6 TE / ad ○ 6 * 6 * 1M = 36M TE per adbreak SSAI: Some numbers
- 21. ● We currently have: ○ 808 defined metrics ○ 165 paging alerts ● Goals: ○ Be proactive ○ Analyze behavior ○ Forensics Monitoring
- 22. Latency in HLS
- 23. R&D: LHLS 1- Creates .ts files on the fly 2- Adds growing files signaling 3- Creates advanced chunklist 1- Simple static files webserver 2- Reads the growing files flag and uses real time chunked transfer for those (CDN!) LHLS: https://medium.com/@periscopecode/introducing-lhls-media-streaming-eb6212948bef 1- Process segment while it is still being received
- 25. R&D: Edge computing possibilities ~0% HIT
- 26. R&D: Edge computing possibilities ~100% HIT
- 27. R&D: Edge computing possibilities Prefetching ON Prefetching OFF
- 28. THANK YOU! Jordi Cenzano | @jordicenzano | jordicenzano