Skip to content
go-libfossil Check-in [6ae0bf4b3d]
Login

Check-in [6ae0bf4b3d]

Overview
Comment:Merge remote-tracking branch 'origin/main' into perf/memo-tree-encoding
Timelines: family | ancestors | descendants | both | main | trunk | perf/memo-tree-encoding
Files: files | file ages | folders
SHA3-256: 6ae0bf4b3d2e6180dff045263f33ef36b0cc766eb8e82e577ecd773a44c3e6de
User & Date: [email protected] on 2026-10-28 22:44:18.000
Other Links: branch diff | manifest | tags
Context
2026-10-28
23:40
Merge remote-tracking branch 'origin/main' into perf/memo-tree-encoding

# Conflicts: # CHANGELOG.md check-in: a90035689e user: [email protected] tags: main, perf/memo-tree-encoding, trunk

22:44
Merge remote-tracking branch 'origin/main' into perf/memo-tree-encoding leaf check-in: 6ae0bf4b3d user: [email protected] tags: main, perf/memo-tree-encoding, trunk
22:44
perf(content): read trees lazily again, kept in the compact encoding

A full read of every tree with the graph made a cold classification on fossil-scm.org's clone three to four times slower, which an origin that starts cold often cannot afford. Walks read a tree when they first need it, as before, and the memo keeps what they read as a treeIndex (interned ids, delta-varint sets, full manifests as differences), replaced on each publish so views read it without the lock. memoTreeBytes now bounds that encoding, which holds the whole history of fossil-scm.org in about 11 MiB; past it the index starts again. HZ-6.2-10 stays partial: trees are still read on first use, not with the graph. check-in: b53551c192 user: [email protected] tags: main, perf/memo-tree-encoding, trunk

21:50
Merge pull request #519 from danmestas/conf/hz-4-1-1-zit-scope

conformance: HZ-4.1-1 scoped to zit and go-libfossil origins check-in: 1455a3803e user: [email protected] tags: main, trunk

Changes