Increase search instance's memory (and core count). #8833
Merged
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
sigurdm
approved these changes
Jun 26, 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.
The production search instances report about 6.5-7 GB memory being used, and about 12 GB maximum memory usage, which is happening when the new search isolate is being loaded while the old one is still active. This is very close to the 12.6 GB limit, and the new search isolate also adds a nontrivial amount of memory.
I think we should increase the memory, which can only be done if we also increase the CPU count. This is a must if we must keep the current experiment with the fast-lane search isolate, but even if we roll that back, I think we should increase the memory as we are close to the allocated threshold.
Note: I'll spend some time on the memory usage later, I think we have a few things to optimize (or remove) there.