Skip to content
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

Enable madvise by default for all builds #110159

Merged
merged 5 commits into from
Jul 10, 2024

Conversation

benwtrent
Copy link
Member

This feature flag has been enabled by default for snapshot builds for some time, no significant bumps or changes in rally.

This commit will enable it by default, even in release builds.

@benwtrent benwtrent added >non-issue :Search/Search Search-related issues that do not fall into other categories v8.15.0 labels Jun 25, 2024
@benwtrent benwtrent requested a review from jpountz June 25, 2024 20:05
@benwtrent benwtrent requested a review from a team as a code owner June 25, 2024 20:05
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search (Team:Search)

@elasticsearchmachine elasticsearchmachine added the Team:Search Meta label for search team label Jun 25, 2024
@benwtrent benwtrent added the cloud-deploy Publish cloud docker image for Cloud-First-Testing label Jun 25, 2024
@benwtrent
Copy link
Member Author

@elasticmachine update branch

@@ -58,6 +58,9 @@
# result in less optimal vector performance
20-:--add-modules=jdk.incubator.vector

# Enable random access flags via madvise
-Des.madv_random_feature_flag_enabled=true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think typically when we want to enable something by default that was previously behind a feature flag, we simply remove the feature flag. In either case, I don't think we'd want this option in jvm.options but rather in SystemJvmOptions. @rjernst might provide more insight here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's right, we should remove the feature flag to "enable" it permanently. If the intent is for users to be able to disable this, then it should be moved from a feature flag to a setting.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

roger! I will just remove the flag :)

@benwtrent benwtrent removed the cloud-deploy Publish cloud docker image for Cloud-First-Testing label Jul 9, 2024
Copy link
Contributor

@ChrisHegarty ChrisHegarty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with the complete removal of the feature flag. LGTM

@benwtrent
Copy link
Member Author

@elasticmachine update branch

@benwtrent benwtrent added the auto-merge Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Jul 10, 2024
@elasticsearchmachine elasticsearchmachine merged commit 4a77e06 into elastic:main Jul 10, 2024
15 checks passed
@benwtrent benwtrent deleted the feature/enable-madvise branch July 10, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) >non-issue :Search/Search Search-related issues that do not fall into other categories Team:Search Meta label for search team v8.16.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants