Comparing Linux OS Image Update Models
summary
Compares four updaters (Mender, RAUC, swupdate, Torizon) on Toradex Verdin NX8M‑Mini using tcpdump/wire‑shark captures and realistic Yocto builds. Key findings: a one‑byte change on a 350 MB image downloads ~12 MB with OS‑tree vs ~130 MB for dual A/B systems; Delta runs show Mender ~232 KB and OS-tree static deltas ~96 KB on small edits; Chromium upgrade favors Mender; full 6.2→6.5: Mender ~75 MB, others ~115–130 MB, OS‑tree static ~55 MB. Binary tools include xdelta, ca‑sync and zchunk; benchmarks run and reproducible enough to guide choice.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:05OTA update models
- 3:12Dual partition vs OS tree
- 6:22Updaters: Mender, RAUC, SWUpdate, Torizon
- 16:45Benchmark setup
- 18:31Full image update results
- 19:37Delta update results
- 20:41Chromium install performance
- 21:25Chromium upgrade performance
- 21:47Chromium uninstall performance
- 22:07Minor version upgrade results
- 22:48Future work
- 24:38Q&A
related talks
34mComparing Linux OS Image Update Models
56mComparison of Linux Software Update Technologies
41mDelta Updates: Making Updates Leaner
43mUpdate My Board!
43mPractical Experience with Linux A/B Upgrades
45mSoftware Updates for Connected Devices: Key Considerations
44mUpdating an Embedded System with SWUpdate Framework
47mOrchestrated Android-Style System Upgrades for Embedded Linux