docs(reference): add the benchmarks page#54
Open
coderdan wants to merge 1 commit into
Open
Conversation
Publishes the EQL v3 query-performance numbers from cipherstash/benches at /reference/benchmarks, so the performance claims have a docs page to land on: - encrypted-vs-plaintext query latency (exact match and OPE range within ~1.2-1.4x of plaintext, flat from 10k to 10M rows) - the OPE-vs-ORE range/order tradeoff, free-text bloom match, JSON, GROUP BY - ingest throughput, methodology, caveats, and repro steps Every figure is sourced from the public benches report and cross-checked against the plaintext baseline. Ticks the IA checklist item.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Adds
/docs/reference/benchmarks— the performance numbers with methodology, per the IA. Closes the gap where these figures existed only in the external benches repo.Source
Numbers distilled from the public cipherstash/benches EQL v3 suite (PR:
eql-v3-benches), specifically thereport/BENCHMARK_REPORT.md"vs plaintext PostgreSQL" table andreport/V3_COMPARISON.md. Every figure is cross-checked against the plaintext baseline; nothing is restated without a source.What the page covers
0.12 ms (1.3x), OPE range0.12 ms (1.2x), ORE range0.52 ms (5.2x), JSON@>0.40 ms (1.4x),GROUP BY83 ms (2.2x).Verification
bun run buildgreen (694 pages);validate-linksreports no broken links.Notes / scope
/concepts/compare/aws-kmspage yet to cross-link. Left it out rather than restate an unsourced number — happy to add a "key-management throughput" section once that benchmark/page lands.contains10M outlier is a documented plan artifact, flagged as such.