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.

Sign up for GitHub

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

Jump to bottom

Affinity rule to ensure server and frontend-2 are deployed to the same node #1460

Closed
iainsproat opened this issue Mar 15, 2023 · 2 comments
Closed

Affinity rule to ensure server and frontend-2 are deployed to the same node #1460

iainsproat opened this issue Mar 15, 2023 · 2 comments
Assignees
@iainsproat

Comments

@iainsproat
Copy link
Contributor

iainsproat commented Mar 15, 2023 •
edited
Loading

We should have a pod affinity rule to try to ensure server and frontend-2 are deployed to the same node. (though this won't scale)
@iainsproat iainsproat self-assigned this Mar 15, 2023
@fabis94
Copy link
Contributor

fabis94 commented Mar 15, 2023 •
edited
Loading

Reason: If server and frontend-2 are close to each other and the latency between them is low, then the server-side render by frontend-2 will be even quicker and the time to load the 1st page will be reduced for our users. This is because on first load the user only receives pure HTML with all of the GQL calls already pre-made on the server-side.

@iainsproat
Copy link
Contributor Author

Closed in lieu of linear issue: https://linear.app/speckle/issue/WEB-1629/helm-chart-fe2-should-have-affinity-with-speckle-server-pods

@iainsproat iainsproat closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iainsproat iainsproat

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iainsproat @fabis94