Henry/pre-build workspace dependencies in dev Docker images#1107
Open
Henry/pre-build workspace dependencies in dev Docker images#1107
Conversation
Contributor
|
@Henrp cool, but I think only Spring 2026 and Summer 2026 came and they don't have classes. Could you look into this? |
Contributor
Author
|
@ARtheboss staging has 768Mi memory limit while prod has 3Gi. this makes the 'classes-lat-five-years' bulk pull crash mid run (OOMKilled). I think this is why only two semesters out of the rest of the semester was pulled. I think to solve this we need to upgrade memory limit to ~2Gi, but im not really sure if this is necessary because its for staging and we don't really need all the data for testing. We have around 1.4Gi free from the 15Gi total so upgrading is also an option. |
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
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.
Summary:
CrashLoopBackOff) and populated it with data via manual datapuller
runs (only 2019 data right now). Cronjobs fill in the rest of the data at 4am.
startup is fast enough to not timeout the 300s CI rollout wait.
Testing:
now, Rest will populate after tonight's 4am cronjobs
the backend rollout completes without the 300s timeout error