Publish corrected 10GB benchmark result and simplify docs#5
Merged
sushanthpy merged 3 commits intoMay 30, 2026
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
2 participants
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.
Summary\n- publish the corrected native 10GB benchmark result as checked-in artifacts\n- simplify benchmark docs to emphasize final published conclusions\n- add a short README highlights section for the latest quality and scale takeaways\n\n## Why\nThe earlier 10GB search number reflected a bad harness path rather than the real steady-state search behavior. This PR makes the corrected native result visible and cleans up the benchmark repo surface so readers see the final story quickly.\n\n## Included\n- corrected 10GB native benchmark artifacts\n- simplified server benchmark status doc\n- simplified staged benchmark plan doc\n- README benchmark highlights section