graph: reduce memory allocations#494
Merged
Merged
Conversation
fschade
approved these changes
Mar 27, 2025
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
3885b8c to
8c5af66
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
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.
While investigating #485 I noticed that we are constantly allocating memory to build the list of available roles. This PR changes this to be done once at startup.
This does not fix the PR mentioned above. It is just something I noticed while trying to find out where all the GetUser requests are coming from.
cc @fschade