Repository navigation
Conversation
…hared process store, schedule from the host The client export spent 183 of its 196 minutes (main a1357b5, 4 vCPU, 16 GB) compiling the 9 preservation certificates one after another, and every change re-proved all of them. The pin moves to LexLean claude/export-parallel-store-2 (2bf5c1e plus two commits): - certificates compile in the frontiers of their imports at the export width, within the memory budget (SPEC 22.11 item 6); - every Lean process goes through a store keyed by the content identity of its module and all it imports (SPEC 22.13), digest-checked on restore; - certificates are named by their root's lowered program, and certificate A imports only the modules its terms name, so a root a change does not reach keeps its certificates and is not proved again. client-export.mjs runs it at the host's width (availableParallelism) and available memory, schedules from generated/rust/export-hints.json (the last export's per-process wall time and peak, rewritten after each export), uses the store UORC_EXPORT_STORE (default .lexlean/store; lanes share /mnt/project-files/export-store), and prunes it least recently used so it never holds more than the free space it leaves. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3QjGTCZCDMLxRDZ33Q
…tore Cold export on this branch: 9169 s (baseline 3 h 16 min at width 1). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3QjGTCZCDMLxRDZ33Q
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3QjGTCZCDMLxRDZ33Q
afflom
marked this pull request as ready for review
November 16, 2026 08:03
…olerate concurrent store writers The client export under the final LexLean revision: cold 154 min (the two largest certificates run one after another under the memory gate), warm no-change 5.0 min with the same result id. The store walk skips entries another export is writing or pruning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3QjGTCZCDMLxRDZ33Q
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Alex · project thread
Result (measured, 4 vCPU / 16 GB)
The warm run published the same result (
e5f0d61a…) as the cold run, with 281 processes restored from the store and 3 run. Of the 5.1 min that remains, certificate generation takes 171 s (Rust, in-process), which is the next measured distance. The first warm run took 7.8 min (466 s), because it restored from a store on the network mount that had not been read yet.In the cold run the decompress and search B certificates (8.9 GB and 7.7 GB peak) compiled and replayed one after the other, because together they exceed the declared memory. Those two set the cold time.
Where the export's time went before
Every certificate A imported all 78 modules, and every certificate was named after the project's semantic id, so any change re-proved all nine.
What changes
The pin moves to LexLean
claude/export-parallel-store-2at c06c769 (LexLean#558, on 2bf5c1e):LEXLEAN_VERIFY_STORE, SPEC 22.13). The key is the tool, the Lean executable digest, the normalized argv, and the Merkle κ of the module text and everything its imports reach. Restored files are digest-checked; the published bytes are the same with and without the store..laketree, and the normalized environment. A module that neither the stage nor the toolchain holds is a miss, and so is every module that imports it.scripts/client-export.mjstakes every scheduling input from the host or from the last measurement: width =os.availableParallelism(), memory =MemAvailable, hints =generated/rust/export-hints.json(rewritten after every export), store =UORC_EXPORT_STORE(default.lexlean/store, pruned least recently used within free space). Lanes share/mnt/project-files/export-store. The prune walk skips entries that another export is writing or pruning at the same time.The approach follows the PrismPM factory's identity-by-closure receipts (#678/#681/#682) and verdant-engine's input-addressed κ cache.
On LexLean's
examples/production-coveragethe attestation is identical at width 1, at width 2 with a cold store, and with a warm store (683 s, 387 s, 12 s; 24 s after a one-module edit, with 5 of 298 certificate processes re-run).https://claude.ai/code/session_013Asa3QjGTCZCDMLxRDZ33Q
Generated by Claude Code