Skip to content

Delta updates

A delta update sends only the parts of a build a device does not already have. On customer fleets the median patch is 18% of the full installer size.

Tiles

Verdel splits every file in a build into content-defined tiles with a target size of 64 KB (minimum 16 KB, maximum 256 KB). Tile boundaries come from the content, so adding bytes in the middle of a file shifts only the tiles around the edit. Each tile is addressed by its SHA-256 and compressed with zstd level 12.

Patch chains

At publish time Verdel computes patches from the previous 12 releases of each platform to the new one. A device receives the patch from the exact version it runs. Devices more than 12 releases behind get the full installer, as do devices where the patch would exceed 70% of the full size, since the extra round trips cost more than they save.

SituationDevice receivesWhy
One release behindSingle patchSmallest, most common case
Two to 12 releases behindDirect patch from its versionComputed at publish time, not chained on the device
More than 12 behindFull installerNo patch stored
Patch larger than 70% of fullFull installerFaster to fetch one file
Local files modified by userMissing tiles fetched individuallyVerification fails on those tiles only

Verification

Every tile is checked against the manifest before it is written. The result of applying a patch is verified against the SHA-256 of the whole target, and the previous version is kept on disk until the new one has launched successfully once, so an update that cannot start rolls back without a network.

Measuring savings

verdel stats acme-notes --channel stable --last 30d
releases        4
device-updates  1,204,886   delta 83.1%   full 16.9%
delivered       39.7 TB      without delta: 214.0 TB
median patch    9.8 MB       p95 41 MB

Making builds diff well

  • Avoid embedding build timestamps and absolute paths in binaries; they change every tile.
  • Do not re-compress assets into one archive. Ship the directory and let Verdel tile it.
  • Keep debug symbols out of the installer and upload them separately as symbols.
  • Use reproducible builds. Identical inputs should give identical outputs, so unchanged code produces unchanged tiles.