chore: new cached routes percent 30% #898
Merged
Conversation
This file contains 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
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
cgkol
approved these changes
Nov 1, 2024
Graphite Automations"Request reviewers once CI passes on routing-api repo" took an action on this PR • (11/01/24)4 reviewers were added and 1 assignee was added to this PR based on 's automation. |
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.
with 10%, I can see caching routing lambda concurrent executions going up, meanwhile routing lambda concurrent executions going down a bit:
routing dashboard wise, I haven't see latency improvement yet:
This motivates me to go higher enough percent, in a hope to see if the quote endpoint latency can show difference.