Skip to content

test(projects): the large document is read once on Memo 0.80.0 - #180

Merged
leemour merged 1 commit into
mainfrom
perf/large-document-read-once
Oct 20, 2026
Merged

leemour merged 1 commit into
mainfrom
perf/large-document-read-once

Conversation

@leemour

@leemour leemour commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Why

#178 showed the fixed release finding the large document, but charging 476,300 bytes for one 95,200-byte document: each of its five matching lanes read it again. cli-core#1676 (Core 0.369.0, Memo 0.80.0) skips that read. Did it work on the released packages?

Results

Same script and invented document, exact registry Memo 0.80.0 / Core 0.369.0 / Base 0.47.1:

Memo 0.79.0 Memo 0.80.0
Charged bytes 476,300 95,260
Reads 10 6
Found / complete 1 / true 1 / true

What

  • result-read-once.json with the new run.
  • after-fix.mjs now pins Memo 0.80.0 / Core 0.369.0. The README says which commit produced the 0.79.0 result.
  • README table, index line and changelog.

Testing

Ran the commands in the README. lint, docs:check, docs:lint, docs:spell and standards:check pass.

🤖 Generated with Claude Code

Rerun of after-fix.mjs on exact registry Memo 0.80.0 / Core 0.369.0: the
95,200-byte document matched by five lanes now charges 95,260 bytes in six
reads, the document once (476,300 bytes in ten reads on Memo 0.79.0). The
script now pins those versions; the 0.79.0 result stays as recorded.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@leemour
leemour merged commit 9dc2c61 into main Oct 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant