|
Size: 1360
Comment:
|
Size: 1420
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 24: | Line 24: |
| * 6 bytes: offset (allows for 256TB of compressed history per file) | |
| Line 25: | Line 26: |
| * 6 bytes: offset (allows for 256TB of compressed history per file) | |
| Line 37: | Line 37: |
| As the offset of the first data chunk is always zero, the first offset is used to indicate revlog version number and flags. | As the offset of the first data chunk is always zero, the first 4 bytes (part of the offset) are used to indicate revlog version number and flags. all values are in big endian format. |
RevlogNG was introduced with Mercurial 0.9.
Deficiencies in original revlog format:
- no uncompressed revision size stored
- SHA1 hash is potentially too weak
- compression context for deltas is often too small
- offset range is limited to 4MB
- some metadata is indicated by escaping in the data
The original index format was:
- 4 bytes: offset
- 4 bytes: compressed length
- 4 bytes: base revision
- 4 bytes: link revision
- 20 bytes: nodeid
- 20 bytes: parent 1 nodeid
- 20 bytes: parent 2 nodeid
72 bytes total
RevlogNG format:
- 6 bytes: offset (allows for 256TB of compressed history per file)
- 2 bytes: flags
- 4 bytes: compressed length
- 4 bytes: uncompressed length
- 4 bytes: base revision
- 4 bytes: link revision
- 4 bytes: parent 1 revision
- 4 bytes: parent 2 revision
- 32 bytes: nodeid
64 bytes total
RevlogNG header:
As the offset of the first data chunk is always zero, the first 4 bytes (part of the offset) are used to indicate revlog version number and flags. all values are in big endian format.
RevlogNG also supports interleaving of index and data. This can greatly reduce storage overhead for smaller revlogs. In this format, the data chunk immediately follows its index entry. The position of the next index entry is calculated by adding the compressed length to the offset.