feat: update max request multiplier to 3 for larger instances #18342
+8
−2
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
increase the number of max requests on large instances (8Gb+) by using a bigger multiplier (1.5 -> 3.0) increase in memory usage is minimal but the increased requests are enough to push ES more, especially on arm instances
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
kruskall
added
the
backport-active-all
marclop
previously approved these changes
Aug 26, 2025
1pkg
previously approved these changes
Aug 26, 2025
max request expected default value went from 22 to 34 for 8gb instances
marclop
approved these changes
Aug 27, 2025
1pkg
approved these changes
Aug 27, 2025
carsonip
approved these changes
Sep 3, 2025
carsonip
reviewed
Sep 3, 2025
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.
Motivation/summary
increase the number of max requests on large instances (8Gb+) by using a bigger multiplier (1.5 -> 3.0)
increase in memory usage is minimal but the increased requests are enough to push ES more, especially on arm instances
Checklist
For functional changes, consider:
How to test these changes
run apm-server in a docker image and set the container memory to < 8Gb
Related issues