Skip to content

Backlog: what a large map's build still spends, and the updateModel scan off the critical path - #1455

Merged
Frotty merged 2 commits into
masterfrom
claude/backlog-build-costs
Oct 13, 2026
Merged

Frotty merged 2 commits into
masterfrom
claude/backlog-build-costs

Conversation

@Frotty

@Frotty Frotty commented Oct 13, 2026

Copy link
Copy Markdown
Member

Docs only (BACKLOG.md). Records what was measured but not changed while profiling a large map's build with the corrected -measure (#1452) and JFR, so the next round starts from the numbers:

  • MPQ, on every run and build: Applying Map Config (1.2 s) and Injecting map data (1.8 s) are mostly two JMPQ3 lookups which are linear per call and called once per file (MpqArchive.localesOf, MpqArchiveWriter.contains); Finalize map (7.8 s, release builds) recompresses every file on one thread. To be fixed in JMPQ3, then the pin bumped.
  • Type check: Guava collections about 11 % of its samples after Name resolution: a package's imported names are looked up, not collected into one table #1451; the dataflow anomaly analysis copies its immutable states on every read and write (about 7 %).
  • Translation to IM: getClassesWithImplementation is 20 %, a member lookup per method per subclass; how a faster version would have to be validated.
  • The updateModel scan item: keeping the WFile hash made the comparisons integer comparisons but did not change the load time, because the scan is off the critical path while parsing is parallel.

…can off the critical path

Records the costs measured but not changed while profiling a large map's
build: the two per-file linear lookups in JMPQ3 behind the map config and the
map data injection, single-threaded recompression of a release map, the
Guava collections and copied dataflow states in the type check, and the
per-subclass member lookups when translating methods to IM. And that keeping
the WFile hash did not speed up a load, as the scan is off the critical path
while parsing is parallel.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-13T09:59:01.792146Z bf3da7e Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

…low subclasses override the method themselves
@Frotty

Frotty commented Oct 13, 2026

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep them coming!

Reviewed commit: bf3da7e618

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@Frotty
Frotty merged commit 768dc92 into master Oct 13, 2026
2 checks passed
@Frotty
Frotty deleted the claude/backlog-build-costs branch October 13, 2026 21:11
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