Skip to content

Revisit automatic heap sizing heuristic for coordinating nodes #88395

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.

Sign up for GitHub

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

Jump to bottom
Open
mark-vieira opened this issue Jul 8, 2022 · 1 comment
Open

Revisit automatic heap sizing heuristic for coordinating nodes #88395

mark-vieira opened this issue Jul 8, 2022 · 1 comment
Labels
:Performance All issues related to Elasticsearch performance including regressions and investigations Team:Performance Meta label for performance team

Comments

@mark-vieira
Copy link
Contributor

As mentioned by @ersinbyrktr in this comment our use of the same heap sizing calculations for data and coordinating nodes may not be the most efficient. We may want to revisit the existing heuristics used here and optimize for coordinating nodes.
@mark-vieira mark-vieira added the :Performance All issues related to Elasticsearch performance including regressions and investigations label Jul 8, 2022
@elasticmachine elasticmachine added the Team:Performance Meta label for performance team label Jul 8, 2022
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-perf (Team:Performance)

@mark-vieira mark-vieira mentioned this issue Jul 8, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Performance All issues related to Elasticsearch performance including regressions and investigations Team:Performance Meta label for performance team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mark-vieira @elasticmachine