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

[ENH] - Lower cost node sizes on GCP Nebari #2452

Closed
Adam-D-Lewis opened this issue May 7, 2024 · 1 comment · Fixed by #2453
Closed

[ENH] - Lower cost node sizes on GCP Nebari #2452

Adam-D-Lewis opened this issue May 7, 2024 · 1 comment · Fixed by #2453
Assignees
Labels
area: user experience 👩🏻‍💻 impact: medium 🟨 This item affects some users, not critical needs: discussion 💬 Needs discussion with the rest of the team provider: GCP type: enhancement 💅🏼 New feature or request

Comments

@Adam-D-Lewis
Copy link
Member

Adam-D-Lewis commented May 7, 2024

Feature description

Note: Prices are at the time of writing and for the us-central-1 region.

The general node on GCP has 8 cpus and 30G of memory (n1-standard-8). This node size costs ($0.38/hr = $275/month), but the most of the time the cpus are doing very little and GCP has the ability to create custom node sizes at the cost of $25/cpu-month and $3/GB-month of RAM (up to 6.5GB/cpu) + $7/GB-month for additional RAM (beyond 6.5GB/cpu).

E.g. If we could get away with a 4 cpu 30GB of RAM node then the cost would be $205/month.

Value and/or benefit

25% Lower fixed costs for using Nebari. It's not clear to me what the ideal resources are for the node group, but it seems likely that we can reduce the cpu amount from 8 to 4 without ill effects. According to Grafana, in the last 7 days, this particular cluster never went beyond 1 cpu used for the general node, and the vast majority of the time needed less than 1 cpu.

Alternatively a e2-highmem-4 "cost optimized" instance with 4 cpus and 32GB costs ~$130/month.

Anything else?

More info on how to create custom machine types at https://cloud.google.com/compute/docs/instances/creating-instance-with-custom-machine-type

@Adam-D-Lewis
Copy link
Member Author

Looking further, it seems easy to change the default node type to E2 instances on GCP and reduce costs by ~50%

@Adam-D-Lewis Adam-D-Lewis self-assigned this May 7, 2024
@viniciusdc viniciusdc added type: enhancement 💅🏼 New feature or request needs: discussion 💬 Needs discussion with the rest of the team area: user experience 👩🏻‍💻 provider: GCP impact: medium 🟨 This item affects some users, not critical labels May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: user experience 👩🏻‍💻 impact: medium 🟨 This item affects some users, not critical needs: discussion 💬 Needs discussion with the rest of the team provider: GCP type: enhancement 💅🏼 New feature or request
Projects
Status: Done 💪🏾
Development

Successfully merging a pull request may close this issue.

2 participants