perf(desktop): replace messages.map with backwards-walk index in streaming handlers#2055
Merged
Merged
Conversation
… in streaming handlers
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
2 participants
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.
Before
Every streaming event (
model.delta,model.final,tool.preparing,tool.intent,tool.result) calledstate.messages.map(m => condition ? updated : m)— iterating ALL messages and creating a full new array on every chunk. 500 messages × 5000 chunks = 2.5M element operations per session.After
Backwards walk from the end (streaming always targets the latest assistant turn) replaces only the target message.
[...state.messages.slice(0, i), updated, ...state.messages.slice(i + 1)]— O(target) not O(all). Spread creates a new array reference without iterating or transforming every element.