Adjust RouteCache to mitigate contention - #998
Merged
Merged
Conversation
Collaborator
Author
|
Some quick testing notes on throughput on
My read is that the lock scoping changes (and refusal to take a write at suspected max capacity) do help in the cases that we have more flows than slots. I'll see about getting some lockstat runs. |
rcgoodfellow
approved these changes
Jul 23, 2026
rcgoodfellow
left a comment
Contributor
There was a problem hiding this comment.
Thanks @FelixMcFelix. Just one non-blocking suggestion here.
FelixMcFelix
force-pushed
the
routecache-tuning
branch
from
July 23, 2026 20:52
9cb8395 to
edc1be4
Compare
Let's introduce contention to actually measure the impact of the next few changes...
FelixMcFelix
force-pushed
the
routecache-tuning
branch
from
July 24, 2026 09:40
edc1be4 to
f21e375
Compare
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.
This PR follows up on the steps outlined in #997. The main changes are to increase the table size, and to minimise the amount of time holding the write lock on a miss by fetching a new route before taking the lock. This includes refusing to attempt an insert on a failed lookup in a full table.
One of the steps outlined in the issue, not evicting present entries, was already implemented.
Closes #997.