github/penpot
1
0
Fork 0
mirror of https://github.com/penpot/penpot.git synced 2026-10-29 05:50:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

📚 Name the three readers that share the summary cache

Browse Source
This commit is contained in:
Álvaro Tejero Cantero 2026-08-14 08:18:53 +02:00
parent 74174deb0d
commit fcaf1945fe
No known key found for this signature in database
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/technical-guide/developer/branching.md
View File

@ -252,6 +252,17 @@ bounds memory (`max-size`, `keepalive`) and never decides correctness, and
a failed computation is not stored, so a broken branch keeps degrading to
zeros with a warning on every listing.
All three readers of these numbers go through `cached-diff-counts` and share
the one cache: `::get-file-branches` (the branch panel), `::get-file-branch-info`
(asked on every file open) and `::get-file-pull-requests` (the review list).
They ask the same question about the same pair, so whichever runs first warms
the others, and none of them realizes main when every row it needs is already
cached. Measured on the 21,169-shape design system with nine open branches and
eight open pull requests: a cold pull-request listing costs 20,073 ms with 9
file realizations and 8 base-snapshot loads, its repeat 3 ms with none, and the
branch listing that follows it pays only for the one branch that has no pull
request.
## The three-way diff engine
`app.common.files.branch-merge` is the heart of the feature. It is a pure,