Scale prod to use bigger instances#238
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We keep putting more users on our servers (🥳), but this is raising load. Previously, I scaled out some extra nodes, but they were all t3.* instance types which are not ideal at all for production use. This PR replaces all of those nodes with a fresh, new set of m7a.2xlarge instances. This is a substantial increase in compute power that also removes the CPU credit metering we have to deal with in T-class instance types.
However, while carefully rolling these changes out, I ran a
pulumi refresh, which brought to light a bug that I have fixed in tb_pulumi. For this reason, I am pinning this to themainbranch; I don't want to involve this code change in other environments.These code changes have already been rolled out.