feat(common): allow specifying concurrency in transactionQueue #2589
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.
After hearing from @Kooshaba about Sky Strife latency, specifically when playing from Japan, I did a bit of testing with a fresh template deployed to Redstone Holesky to find out where some of the latency was coming from. There's quite a few factors at play:
Even though increasing the concurrency will lead to nonce errors, it may be an acceptable trade-off for certain games/applications where its safe to retry after nonce failure and its fine to have somewhat out-of-order operations.