perf: fix extreme lag (20x) when crafting in item-heavy area#8244
Merged
perf: fix extreme lag (20x) when crafting in item-heavy area#8244
Conversation
36b41d5 to
ce586ba
Compare
190f7c9 to
c2194b5
Compare
Assisted-by: gpt-5.3-codex on opencode Co-authored-by: chatgpt-codex-connector[bot] <199175422+chatgpt-codex-connector[bot]@users.noreply.github.com>
c2194b5 to
07f1b1a
Compare
chaosvolt
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose of change (The Why)
fixes #8243
Describe the solution (The How)
ACT_CRAFTactivity and reuse it during craft turns.Testing
spawn a vehicle, fill it with gazillion cargo, craft something. i used private save file from original issue raiser.
result: 32.7s -> 2.7s (12.11x, initial), 1.5s (21.8x, cached)
Checklist
Mandatory
closes #1234in Summary of the PR so it can be closed automatically.mainso it won't cause conflict when updatingmainbranch later.