Differences between revisions 13 and 14
Revision 13 as of 2012-10-25 20:50:58
Size: 4126
Editor: mpm
Revision 14 as of 2015-03-08 04:23:22
Size: 4206
Editor: KevinBullock
Comment: link to GeneralDelta at the top
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:

''This plan has been superseded by [[GeneralDelta]] and [[BundleFormat2]].''


This page is primarily intended for developers of Mercurial.

This plan has been superseded by GeneralDelta and BundleFormat2.

Revlog parent deltas

Improving revlog compression by avoiding deltas between interleaved branches.

1. Introduction

The RevlogNG file format has a few known weaknesses, one of which is the lack of parent deltas. That is, new revisions are always delta'ed against the revision directly before it, when in many cases it makes much more sense to diff against the parent revision instead (e.g. when they're on very different branches). This makes some revlogs very space-inefficient, particularly in very branchy repositories or in repositories that have been converted from some other VCS. This can be seen from the reduction caused by "manual" reordering of the revlog, particularly for the manifest revlog in larger repositories.

2. Implementation

It would be nice to reduce at least some of the inefficiency by being able to delta against the parent revision in cases where that's an easy win. In RevlogNG, revisions can be constructed from taking the (specified) base revision and applying all revisions from that base revision, in a contiguous block, through to the requested revision. This means there's little seek time (seeks, being dependent on disk rotation speeds, are particularly expensive and resistent to Moore's law). Any algorithm for parent deltas should not expand the number of seeks too much, this means the distance between the offset of the base rev and tip should be smaller than a certain amount.

The case of merge revision should be investigated, should we always take the first parent, or can we allow both?

3. Strategy

3.1. Disk format changes

In current revlogs, the implicit rev to delta from is the former revision. If there are cases in which we don't want to do that anymore, we will:

  • use the first unused bit (flag equal to 0x1) to specify that the diff is against the revision specified in base (usually it would be one of the parent)

Of course, we also need all the backwards compatibility trappings (e.g. requires, wire protocol stuff).

3.2. Wire protocol changes

For efficiency (to avoid re-diffing every rev), the WireProtocol can be changed to allow a different changegroup format:

  • either always send a diff vs. the parent
  • or add have a bit that specify the kind of delta

If all the delta from the changegroup are using diff vs. parent, reordering on the fly during a pull/push/clone might be much cheaper (less delta to recompute).

Backward compatibility matrix:

old client

new client

old repo

new repo

old server




new server

old repo




new repo




[1] manifest and filelogs reordered by server on the fly

[2] new bundle format

[3] server reuses deltas from revlogs wherever possible, with reordering, may send parent deltas for deltas it generates at run time, client reuses delta whenever possible except when a config option is activated (which means the clients repo will always stay fully parent-delta-ified).

[4] client redeltas

Note: It might come in handy if we had the following amongst the delta base options:

  • previous in chain,
  • parent1,
  • parent2, or
  • none (meaning we send the full text).

This would help with shallow clones if they ever materialize.

4. Literature


ParentDeltaPlan (last edited 2015-03-08 04:32:20 by KevinBullock)