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

Adopt modern (n2, r5, v5) machines and replace older cost inefficient (n1, r4, v3/v4) #3339

Open
4 of 5 tasks
consideRatio opened this issue Oct 29, 2023 · 0 comments
Open
4 of 5 tasks
Labels
allocation:internal-eng tech:cloud-infra Optimization of cloud infra to reduce costs etc.

Comments

@consideRatio
Copy link
Member

consideRatio commented Oct 29, 2023

Here the kinds of modern isntance types I think we should use, examplified with three equivalent highmem nodes. The n2, r5, and v5 machines are all documented to be Intel Xeon, third generation Icy Lake processors, and their cost per performance is lower than the older options (n1, r4, v3/v4).

Action points

  • Transition n1 to n2
    • Add inline fixme comments next to wherever old nodes are declared in terraform config to upgrade to n2
    • Await the changes be made alongside other changes made in the infra, such as a k8s upgrade
    • UPDATE: 2024-10-23, only pangeo-hubs, which is down, still make use of n1 for non-gpu situations
  • Transition r4 to r5
  • Transition v3/v4 to v5
    • Add inline fixme comments next to wherever old nodes are declared in terraform config to upgrade to v5
    • Await the changes be made alongside other changes made in the infra, such as a k8s upgrade

Historical context

@consideRatio consideRatio changed the title Adopting cost efficient (n2, r5, v5) machines over inefficient (n1, r4, v3/v4) Adopt modern (n2, r5, v5) machines and replace older cost inefficient (n1, r4, v3/v4) Oct 29, 2023
@consideRatio consideRatio added the tech:cloud-infra Optimization of cloud infra to reduce costs etc. label Oct 29, 2023
@consideRatio consideRatio moved this from Needs Shaping / Refinement to Ready to work in DEPRECATED Engineering and Product Backlog Oct 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
allocation:internal-eng tech:cloud-infra Optimization of cloud infra to reduce costs etc.
Projects
No open projects
Status: Ready to work
Development

No branches or pull requests

2 participants