Skip to content
This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions benchmarks/experiments/CAMPAIGN.md
Original file line number Diff line number Diff line change
Expand Up @@ -280,6 +280,7 @@ The repairs in that line are `qOA2` (DuckPGQ, after a duplicate class shadowed t
| 52 | The publish is rehearsed before the data lands: export_web and the six gates on a payload from the October skeleton rows plus a smoke of every new arm; 21 defects fixed (19 undeclared numeric row fields, the sparse table's cold column, e4 reported lost although declared, raw engine errors with unsourced digits in a note) and the lifecycle answer-check note folded from 5,273 to 756 characters | export_web, page_check | done on `repin-prep` (`1a82302f3b`, `ee058b55f9`, `850f607644`) | the remaining refusals come only from stale laptop rows or the laptop host |
| 53 | The 26.10.1 measurement's queue scripts come from a generator (`make_2610_stages.py`): eleven stages in DECISIONS #133's order, five repetitions, the e4 decomposition included, the Python-cost table host-side, the lifecycle expansion last; coverage derived from the runner's lanes and the page's tables, the release pin required, each stage refusing a comparator digest that moved | every arm | written on `repin-prep` (`b04edcd2f5`); queue_lint clean; projected 553 h; launch checklist in `.notes` HANDOFF | DECISIONS #133 |
| 54 | ArcadeDB's TIMESERIES types declare `COMPACTION_INTERVAL 1 HOURS` (the hourly aggregate's bucket), so compaction cuts sealed blocks at bucket boundaries and the aggregate answers from block statistics | ArcadeDB only (embedded and served time-series arms) | **decided 2026-10-04 (the user, #138), CONDITIONAL on upstream confirming it as the intended declaration (ArcadeData/arcadedb#9166)**; if confirmed: change the lane's DDL, disclose it on the page beside the time-series table, teach it in the bindings' time-series docs, and smoke the other two time-series queries (newest reading, one-minute max) for a cost; if upstream says otherwise, record the answer here and keep the default | laptop, relative only (`.notes/bench/repros/perf-timeseries-20261004`, `best-practice-20261004`): on a compacted type PROFILE goes from 0 fast-path and 9 decoded blocks to 16 fast-path and 0 decoded with the same 12 rows; the 12h aggregate's steady p50 from 8.3-10.1 ms to 0.62-1.39 ms and its first call after startup from 632-1,064 ms to 7.8-11.1 ms (pin and newest main). Only ArcadeDB has the knob, hence the user's call and the disclosure. The harness's fixed `SHARDS 4` showed no measurable effect and stays |
| 55 | The graph interactive table's reads get an untimed warm-up on ids disjoint from the timed set, for every engine, before the timed pass; the table prints the warm median and keeps the first query of a session as the cold column; the rows record `read_warmup`, and the "already-warm by construction" sentence (bench_common.NA_COLD_WARM_TXN) is retired for this lane | every engine on the graph interactive table (l2) | **decided 2026-10-04 (the user, approving my recommendation)**: build in `l2_graph.py` before the re-pin and smoke it on the laptop; until then the October page says the first pass includes the JVM's warm-up (own PR from 2026-10-04) | found 2026-10-04 by the graph point-lookup investigation (`.notes/bench/repros/perf-graph-point-20261004`): the lane times its reads twice over the same ids and the table prints the first pass (`l2_graph.py` ~3015-3020, `export_web.py` ~1507). On the October rows (SF1 point p50) ArcadeDB embedded's first pass is 3.59x its second (0.485 vs 0.135 ms), ArcadeDB served 1.46x, Neo4j 2.13x, every other engine 0.89x to 1.10x, so the published 3.2x gap to the median engine (rank 7 of 9) is mostly the JVM compiling the query path; on the second pass it is 0.90x (rank 5 of 9). A Java control (laptop, relative only) shows an untimed warm-up over disjoint ids removes 87-94% of the excess on the pin and on newest main, JDK 25 and 21. DECISIONS #89 already asks for the warm median and PROTOCOL.md requires warm queries disjoint from cold ones, so this implements a standing rule for every engine rather than flattering one |

**Retired: settled with no change, listed so nobody re-opens them.** Raising ArcadeDB's statement-cache settings (a knob only ArcadeDB would get; item 2 removes the literal path instead). The sparse ingest path (already the faster one). Durable commit cost (one sync per commit, equal to SQLite's; not a defect). `expected_edge_count` as a speed lever (no measurable effect; item 1 adopts it only because it is the documented setting). **Done, and off the list:** the dense table's phases partition their total (`setup_s`, since 2026-09-22, BUGS F101), every stage estimates its whole cell against its cap before running (`cell_cost_check.py`, BUGS F74), one engine wears one version per page (`version_consistency_check`, a publish gate, BUGS F61), and `queue_lint` refuses the process-name wait that only holds for one exact launch line (BUGS F59; every October stage waits on its predecessor's ALL-DONE marker).

Expand Down
Loading