Update memory allocation and container parallelisation#405
Merged
Conversation
Adjusted memory usage based on observed caps for the non-crashing containers, and estimates for the crashing containers. Parallelisation for the crashing containers has been reduced: for lakify 10 > 3, for Solrize (set via GitHub env vars) 4 > 2.
Bjwebb
approved these changes
Jun 11, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 memory usage of some containers scales with document size, because there is no streaming, and in June 2026 a set of four large documents ended up repeatedly crashing the workers in the Solrize stage. This PR and some alterations to GitHub env vars: