Feat/json benches - #2
Closed
coderdan wants to merge 6 commits into
Closed
Conversation
- Add bench:ingest:json-ste-vec-small-gin task to benchmark ingest with pre-created GIN index - Add parameterized record counts (default 500,1000,10000, override via arg) - Update _run task to truncate table before each hyperfine iteration - Fix setup-db to create postgres database if it doesn't exist - Add .env sourcing to ingest tasks for DATABASE_URL Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
5 tasks
Contributor
Author
coderdan
added a commit
that referenced
this pull request
Jul 9, 2026
… + field_gt Addresses PR #23 review (James's items #1 and #2): - setup-db-v3 now installs the pinned eql-3.0.0-alpha.3 release bundle instead of building from a local eql_v3 checkout. alpha.3 moved the per-domain types eql_v3.* -> public.* and removed jsonb_query, so the whole v3 surface is migrated to public.<type> (schema_v3.sql, sql/indexes, *_v3 benches, encrypt binaries, src/v3.rs); eql_v3.* FUNCTIONS (eq_term/ord_term/match_term/ord_ope_term/ore_cllw/jsonb_*) are unchanged. - Verified no bench/index/schema calls a moved eql_v3_internal extractor (hmac_256/bloom_filter/ore_block_256/ope_cllw) directly — item #2. JSON bench now queries through the named EQL JSON functions rather than raw jsonb @>/-> operators: - contains/extractor: eql_v3.jsonb_contains(value, $1) on GIN(eql_v3.jsonb_array(value)) - field access: eql_v3.jsonb_path_query_first(value, sel) feeding eql_v3.eq_term / eql_v3.ore_cllw - new scenario json/field_gt/functional: the encrypted `x->'y' > 10` range query -- `>` on public.jsonb_entry inlines to ore_cllw compare, reusing field_order_idx (no new index). Re-ingested + re-ran the JSON tiers 10k-1M-10M against alpha.3 in an isolated DB and regenerated report/V3_COMPARISON.md + report/BENCHMARK_REPORT.md. contains/functional @10m improves 3.36ms -> 1.05ms (jsonb_array recipe). Non-JSON v3 numbers remain the alpha.2-equivalent baseline pending a full re-baseline (flagged by a "Re-baseline status" banner in the report).
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.
No description provided.