Performance: feat - parallelize launch and refresh network requests - #2312
Open
JohnathanWhite wants to merge 3 commits into
Open
Performance: feat - parallelize launch and refresh network requests#2312JohnathanWhite wants to merge 3 commits into
JohnathanWhite wants to merge 3 commits into
Conversation
Balances were awaited behind roughly nine serial round trips: one token-list GET per supported chain, two fiat-rate GETs, then per-key and per-read-only-wallet status calls. These are independent, so they now run together. Per-chain and per-chunk failures are isolated rather than aborting the whole effect, and rates this cycle did not produce are carried forward instead of erased.
Collaborator
|
follow-up: JohnathanWhite#11 |
…uests-followup Wallet: Enhancement - parallelize balance refresh
JohnathanWhite
marked this pull request as ready for review
August 25, 2026 21:00
Collaborator
|
Already implemented here: #2241. We can close this one. |
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.
Balances were awaited behind roughly nine serial round trips: one token-list GET per supported chain, two fiat-rate GETs, then per-key and per-read-only-wallet status calls. These are independent, so they now run together. Per-chain and per-chunk failures are isolated rather than aborting the whole effect, and rates this cycle did not produce are carried forward instead of erased.