Repository navigation
[AUTOMATED] Compact cold completed-decode cache entries - #208
Merged
Merged
Conversation
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.
[AUTOMATED]
Scope
Reduce retained memory in the existing completed-decode cache while preserving every cached result and its fallback/budget semantics.
This improves storage of the existing FID/consumer shared results. It does not add no-return/FID cross-analysis decode sharing. Querying all functions can still reach the prior expanded-IR memory cost; no uniform memory cap or all-function memory reduction is promised.
Standalone on main 064a857 (PR #207). Draft #203/#204 and DecBench #103 remain separate.
Measured evidence
Three alternating pairs on the same large six-function stripped batch, default workers:
Fresh processes/no persisted result cache; same resources and inputs; no own builds/tests/profilers during timings. OS caches and scheduling are uncontrolled. No guest execution, score/ranking, whole-corpus speed or cross-tool semantic-equivalence claim.
Validation
See docs/proposals/2026-10-15-completed-decode-storage.md and docs/validation/completed-decode-storage-performance.{md,json}. Exact hashes, per-run results, coverage bounds and reproduction are included. Full local artifacts: benchmark/artifacts/performance/2026-10-15-decode-storage/.
Datasets