Conversation
Signed-off-by: Lihua <1017343802@qq.com>
Signed-off-by: Lihua <1017343802@qq.com>
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.
Refs #4224. Design and the unmodified failed qualification evidence were recorded first in #4224 (comment).
Goal and delivered outcome
The formal 1 MiB, 10k/100k SQLite D2 run on measurement source
e99a83b63c149685625ecc80e5065c31b2ad36d6failed the existing read budgets: at 100k commits,readReceiptp95 was 269.03 ms (limit 50 ms) andscanCommitted(100)p95 was 801.81 ms (limit 250 ms). The 64 KiB, 100k/300k headroom run had no failed budget rows. Both reports remain historical evidence; this PR does not relabel either result.SQLite v2 verifies every retained row from the covering checkpoint. With a stable 1 MiB projection, each row repeatedly canonicalized the same long JSON string for the exact state and commit SHA-256 proofs. A real SQLite 128-commit probe reproduced about 302 ms for a window-end receipt and 503 ms for a 100-row scan; raw indexed SQL was under 1 ms. CPU samples concentrated in canonical byte generation.
This PR retains the exact v0 proof bytes while reusing bounded encodings of repeated long strings within one verification or archive-audit call. A later empty delta reuses its verified predecessor state digest, still compares the row's declared digest and parent lineage, and still recomputes the full per-row commit proof. The first commit always derives its own state digest. No cache crosses a read call.
Scope and compatibility
Verification
git diff --checkpassed.loopx canary premerge --from-git-diff --git-diff-base origin/mainpassed: 3 direct checks, 5 catalog checks, 8 risk-profile checks, zero failures and zero manual holds. Its temporary local dependency link was removed before push; the tracked diff contains only the five paths above.A full reference-runtime
matched-1m10k/100k rerun on this exact head is still required. Retain the failed row if that rerun misses either threshold. Domain workload, stable RSS, large-history recovery, 24-hour consumer lag, restore/upgrade/rollback, OS/runtime coverage, the natural-time soak and provider promotion remain separate D2 holds. No default-provider change or live-Goal migration is requested.Future-facing pass
The bounded encoding cache stays with the canonical codec owner and is consumed only by SQLite verification. It removes repeated proof work without introducing a second semantic owner or a speculative persisted proof format. Further proof-format work should follow measured real-workload gaps and a separate compatibility review.