Skip to content
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

Tune facia-rendering And tag-page-rendering #11441

Open
JamieB-gu opened this issue May 17, 2024 · 1 comment
Open

Tune facia-rendering And tag-page-rendering #11441

JamieB-gu opened this issue May 17, 2024 · 1 comment

Comments

@JamieB-gu
Copy link
Contributor

Previously we had a single stack for rendering fronts and tag pages: facia-rendering. In #11421 we created a new stack, tag-page-rendering, and sent all tag page traffic to that. We did not change the size (number of instances) or scaling policy of the facia-rendering stack, and we created the new tag-page-rendering stack using exactly the same rules.

As a result, both stacks now have different traffic patterns to what those rules were optimised for. facia-rendering now serves only fronts traffic, and tag-page-rendering serves only tag page traffic.

Therefore we should tune the size and the scaling policy of both stacks to suit their new traffic patterns. This will likely at least mean reducing the minimum number of instances for both.

@JamieB-gu JamieB-gu added this to the Health milestone May 17, 2024
@alinaboghiu
Copy link
Member

We should pull this into our next health sprint in June

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Next Sprint
Development

No branches or pull requests

3 participants