Repository navigation
docs: publish native cold-read result report - #2
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.
Publish the native financial-storage cold-read results and link the report from the README. The report separates embedded and server delivery, includes short/bulk latency, memory, disk, Scalar results and cache-control limits.
Publication scope is deliberately limited to two Markdown files. Test code, raw archives, source snapshots, credentials and deployment/environment configuration remain local. FastK core and public APIs are unchanged.
Validation: 57,800 Kline and 125 Scalar requests independently checked for exact contents, zero selected page residency and positive guest storage I/O; report values checked against audited summaries; git diff --check passes.