Skip to content

clanker: note that decode-cache conflicts change interpreter speed per boot - #720

Open
steigr wants to merge 1 commit into
techomancer:mainfrom
steigr:feature/decode-cache-conflicts-note
Open

steigr wants to merge 1 commit into
techomancer:mainfrom
steigr:feature/decode-cache-conflicts-note

Conversation

@steigr

@steigr steigr commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

clanker: note that decode-cache conflicts change interpreter speed per boot

The interpreter's decode cache keeps 64 physical pages, direct-mapped on
a hash of the page number. Which text pages collide depends on where an
SMP IRIX boot placed the program's, libc's and its own text, so the same
build ran a guest awk 64-67 s in some Tezro boots and 74-110 s in others,
with the re-decode share at 3-8% of host samples in the slow ones. With
256 pages the variance went away. The note records the measurement and
the rule: compare interpreter builds over several boots and check the
decode share in a profile before calling a difference a regression.

Docs only: an agent note in clanker/ and its INDEX.md line. No code change.

🤖 Generated with Claude Code

…r boot

The interpreter's decode cache keeps 64 physical pages, direct-mapped on
a hash of the page number. Which text pages collide depends on where an
SMP IRIX boot placed the program's, libc's and its own text, so the same
build ran a guest awk 64-67 s in some Tezro boots and 74-110 s in others,
with the re-decode share at 3-8% of host samples in the slow ones. With
256 pages the variance went away. The note records the measurement and
the rule: compare interpreter builds over several boots and check the
decode share in a profile before calling a difference a regression.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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