This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Repository navigation
Benchmark page: bindings cutoff 26.10.2, index-before-load sentence, three declarations - #397
Merged
Merged
Conversation
…three declarations The "newer Python bindings" line is keyed on 26.10.2, the first wheel that carries the bindings changes (all five PRs are in the 26.10.2 tag and the PyPI wheel's sources are byte-identical to it). Arms that define their index before the first row are named in one sentence under each table with an index s column, from the rows' index_before_load flag plus a report-time list for the arms whose adapters do not set it. Two global declarations (index order, pinned JVM heap) and one for the graph view's Message supertype, which the export refuses on 26.11.1 rows that still lack it. Closes #396 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
….11.1 re-measure and go on in the next instrument version, with every touched engine re-measured (#396) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 21, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes #396
Report-time changes to the benchmark page generator (
benchmarks/experiments/export_web.py). No measurement code, stage file or stored row changes._BINDINGS_FASTER_FROMgoes from26.11.1to26.10.2. #277, #281, #286, #295 and #320 are all ancestors of the26.10.2tag, the release run for that tag built the PyPI wheel, and the wheel's Python sources are byte-identical to the tag's, so a26.10.2embedded row already contains the bindings speedup and must not be told it predates it. The26.10.1rows still get the line, and the ts_doc out-of-memory declaration, keyed on the same constant, still describes only wheels below26.10.2, which is where #295 landed.An index defined on an empty type before the load times as a few hundredths of a second and read as a free index (
arcadedb_ts_docshows anindex sof 0.04 s against a 27 s load). The page never readindex_before_load._index_before_load_notesnow prints one sentence under each table with anindex scolumn naming the arms that define their index before the first row: the arms whose rows carry the flag (SurrealDB), plus_INDEX_BEFORE_LOAD_REPORTEDfor the arms whose adapters do not set it (ArcadeDB's embedded and served document time-series arms, ArangoDB's time-series arm, SurrealDB's embedded cross-model arm). The rule is the same for every engine. Arms that also build a larger index after the load (ArcadeDB's cross-model arm:Product(pid)first, the vector index after) print a realindex sand are not listed. I checked everyindex_timersite in the lane adapters; the graph and sparse tables print noindex scolumn, so they show nothing to misread.Three declarations.
OCT_PROSE["GLOBAL"]["index_order"]says ArcadeDB's maintainers advise creating indexes after a bulk load and the ArcadeDB rows create most of theirs before it.jvm_heapsays the JVM engines run with the initial heap pinned to the maximum heap, against ArcadeDB's guidance for measuring memory._gav_supertype_notedeclares that the Graph Analytical View lacks theMessagesupertype while the rows are26.10.x, because listing it returns a wrong count for one graph query there, and it refuses a26.11.1-or-later row whosegav_typesstill lacks it, so the26.11.1measurement cannot be published with the stale list. That guard sits in the export, not inl2_graph.py, because a harness change needs its own pull request; it carries aREMOVE WHENline.Not done here: the tracked
results/web_benchmarks*.jsonpayloads are not regenerated, since they are built from the campaign's run log, which is not in the repository, and the next stage landing regenerates them.Checks run, from
benchmarks/experimentswithuv run: the whole experiments test directory (765 passed, 14 skipped), including the newtest_index_before_load_note.pyandtest_gav_supertype_note.pyand a new case intest_next_remeasure_line.py; the repository's pre-commit on the six changed files.🤖 Generated with Claude Code