-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase size of facia-rendering
app instances
#10641
Conversation
Hello 👋! When you're ready to run Chromatic, please apply the |
facia-rendering
appfacia-rendering
app instances
Size Change: 0 B Total Size: 760 kB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
t4g.medium increases the available memory and IO (slightly) but not the cpu count.
I believe DCR is cpu bound rather than memory but its still worth trying to assess the impact.
Ah, thanks Ravi - that's useful to know and think about. I'm just in the process of putting together a dashboard to try to understand the impact of this change but we may well have to up the number of CPUs here. |
@cemms1 I also remembered because DCR is a single threaded process it will only use one CPU. If we want to take advantage of more CPUs we will want to resurrect cluster mode for t4g.xlarge: #9321 |
What does this change?
Updates
facia-rendering
EC2 instances to use a T4G medium rather than a T4G small.Why?
We've been seeing a lot of DCR Timeout exceptions on the
facia-rendering
app since splitting the DCR traffic. This PR aims to reduce these errors.