-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Add a faster path for single default project retrieving #123662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
elasticsearchmachine
merged 3 commits into
elastic:main
from
ywangd:get-project-optimization-for-single-default
Feb 28, 2025
Merged
Add a faster path for single default project retrieving #123662
elasticsearchmachine
merged 3 commits into
elastic:main
from
ywangd:get-project-optimization-for-single-default
Feb 28, 2025
Conversation
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
This PR makes single default project retrieving faster by using a single element map instead of a regular hash map.
Pinging @elastic/es-core-infra (Team:Core/Infra) |
…ion-for-single-default
tvernum
approved these changes
Feb 27, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…ta.java Co-authored-by: Tim Vernum <[email protected]>
ywangd
added a commit
to ywangd/elasticsearch
that referenced
this pull request
Feb 28, 2025
We can avoid using the volatile field when there is only a single default project. Relates: elastic#123662
ywangd
added a commit
to ywangd/elasticsearch
that referenced
this pull request
Feb 28, 2025
No need to create new instances for the default project-id sent across the wire. We can use the singleton field which should speeds up key comparsion for Map.get operations. Relates: elastic#123662
elasticsearchmachine
pushed a commit
that referenced
this pull request
Mar 5, 2025
No need to create new instances for the default project-id. We can use the singleton field which should speeds up key comparsion for Map.get operations. Relates: #123662
georgewallace
pushed a commit
to georgewallace/elasticsearch
that referenced
this pull request
Mar 11, 2025
No need to create new instances for the default project-id. We can use the singleton field which should speeds up key comparsion for Map.get operations. Relates: elastic#123662
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-merge-without-approval
Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!)
:Core/Infra/Core
Core issues without another label
>non-issue
Team:Core/Infra
Meta label for core/infra team
v9.1.0
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 makes single default project retrieving faster by using a single element map instead of a regular hash map.