Skip to content
This repository was archived by the owner on Nov 21, 2026. It is now read-only.

/next page: say what the next measurement re-measures and when - #148

Merged
tae898 merged 1 commit into
mainfrom
page-notes-next-measurement
Oct 4, 2026
Merged

tae898 merged 1 commit into
mainfrom
page-notes-next-measurement

Conversation

@tae898

@tae898 tae898 commented Oct 4, 2026 •

Copy link
Copy Markdown

Closes #147.

Three generated sentences, each keyed on the rows so it leaves the page when the next measurement's rows arrive:

  • Graph interactive table (replaces "already-warm by construction"): the read columns are the first of two passes over the same start persons and include each engine's warm-up, which on the JVM engines includes the JVM compiling the query path; the next measurement adds a disjoint untimed warm-up, prints the warm median, and adds a cold column (CAMPAIGN row 55). Shown while any October l2 row lacks read_warmup; the JVM engines are named from the rows' recorded heap.
  • Durability table: ArcadeDB's waiting runs were set to txWalFlush=2 (an fsync); the next measurement uses txWalFlush=1, a data-only sync like SQLite's FULL setting (CAMPAIGN row 5). Checked: SQLite 3.46.1 in python:3.12-slim (the bench image's base), WAL mode, synchronous=FULL, 100 commits made 109 fdatasync calls and no fsync.
  • Page level: the next measurement runs after this one, on the next ArcadeDB release with every other engine at its latest stable release; it covers the re-run cells and the changes in the table notes. Shown while the ArcadeDB rows are a development build and the page defers something.

CAMPAIGN row 55 also gains the condition that rows recording read_warmup stop stamping cold_warm_na.

The payload is regenerated from the tracked rows with the procedure land_stage uses (steps 2 and 3 of refresh_web_page.py); before the change the same procedure reproduced the tracked payload byte for byte, and after it no cell, entry, table, or column changed. Gates: equivalence, provenance, fairness, version consistency, version pin, and structure ok; page_check --preview against the real site exits 0 with 0 condition findings.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DeKEhHXJTy1H1GgbfBZ8mL

- Graph interactive table: replace the false "already-warm by construction"
  sentence with what the read columns are (the first of two passes, which
  includes the JVM's warm-up on the JVM engines) and what the next
  measurement changes (CAMPAIGN row 55). Keyed on rows without read_warmup.
- Durability table: say ArcadeDB's waiting runs were set to txWalFlush=2 (an
  fsync) and the next measurement uses 1 (fdatasync, like SQLite FULL in WAL
  mode: 100 commits = 109 fdatasync, 0 fsync, SQLite 3.46.1 in
  python:3.12-slim). Keyed on the durability text the rows record.
- Page level: the next measurement runs after this campaign, on the next
  ArcadeDB release with every comparator at its latest stable release.
  Shown while the ArcadeDB rows are a dev build and something is deferred.
- CAMPAIGN row 55: rows that record read_warmup must stop stamping
  cold_warm_na.

Payload regenerated from the tracked rows; no cell, entry, or column
changed. Gates: equivalence, provenance, fairness, version consistency,
version pin, structure ok; page_check against the real site rc=0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DeKEhHXJTy1H1GgbfBZ8mL
@tae898
tae898 merged commit c91362f into main Oct 4, 2026
2 checks passed
@tae898
tae898 deleted the page-notes-next-measurement branch October 4, 2026 07:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

/next page: say what the next measurement re-measures and when (graph warm-up, ArcadeDB strict sync)

1 participant