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

Why is Hetzner default instance CPX11 instead of CX22? 💭 #834

Closed
nelsonic opened this issue Dec 9, 2024 · 7 comments · Fixed by #835
Closed

Why is Hetzner default instance CPX11 instead of CX22? 💭 #834

nelsonic opened this issue Dec 9, 2024 · 7 comments · Fixed by #835
Labels
question Further information is requested

Comments

@nelsonic
Copy link
Contributor

nelsonic commented Dec 9, 2024

G'Morning @vitabaks 👋,
Hope this message finds you well. 👌

Busy setting up a Postgres cluster using autobase 🫶
Noticing that the default instance type is CPX11 and no way to switch to a more cost effective instance type...

image

The CPX11 instance type has only 2 GB RAM + 2 vCPU and costs €3.85/month

image

The CX22 has 4 GB RAM (the same 2 vCPU) and is cheaper (€3.29) per month:
image

Ref: https://www.hetzner.com/cloud/

hetzner-CX22-instance-cheaper

would be good to get some clarity on why the cpx11 instance type is the default. 🤷‍♂️
and if there's no strong reason for it, would you accept a PR allowing people to select the CX22?

Note: there is a Reddit thread explaining the difference in instance type;
One uses Intel CPU whereas the other uses AMD 🧠

https://www.reddit.com/r/hetzner/comments/1gwggv8/cx22_vs_cpx11/ 🔗
image

I'd argue that having double the RAM to store more data in-memory and cache queries results
has a bigger advantage than a marginally faster processor.
But you sir, are the Postgres Expert, so I defer to your experience. 🙏

Thanks. 👌

Note: using the default CPX11 instance type for the screencast I'm working on for now ... 📺
But would prefer to use CX22 for our actual servers where RAM is more important than an AMD CPU.
@vitabaks
Copy link
Owner

vitabaks commented Dec 9, 2024 •
edited
Loading

Hi @nelsonic

The CPX11 is a shared CPU instance, added specifically for testing purposes. For production, we recommend using dedicated CPU instances.

However, if needed, you can manually add the instance types you require to the console database in the cloud_instances table.

Related #784

@vitabaks vitabaks added the question Further information is requested label Dec 9, 2024
nelsonic added a commit to nelsonic/autobase that referenced this issue Dec 9, 2024
@nelsonic
Add CX22 instance for Hetzner closes vitabaks#834
782c5de
@nelsonic nelsonic mentioned this issue Dec 9, 2024
Merged
3 tasks
@nelsonic
Copy link
Contributor Author

nelsonic commented Dec 9, 2024

Totally agree that a prod cluster should be Dedicated CPU. 🏎️ 👌
But for a hobby or test cluster, price is king. 🤑

image

For prod we will be running fully Dedicated resources:
https://www.hetzner.com/dedicated-rootserver/matrix-ax/
image

e.g: AX41-NVMe: https://www.hetzner.com/dedicated-rootserver/ax41-nvme
image

Which we will deploy via the "Your Machines" option:

image

But this is a more advanced usecase so, for now, we just want the baseline for our deployment tutorial/screencast. 😉

Line to be added:

('hetzner', 'Small Size', 'CX22', 2, 4, 0.0052, 3.29, '€', '2024-12-09'),

PR: #835 :shipit:

@vitabaks
Copy link
Owner

vitabaks commented Dec 9, 2024

I get you, it makes sense.

nelsonic added a commit to nelsonic/autobase that referenced this issue Dec 9, 2024
@nelsonic
Update 20241205103951_2.1.0.sql with Hetzner Shared vCPU instances in…
ee9b413 
… USD vitabaks#834
@nelsonic
Copy link
Contributor Author

nelsonic commented Dec 9, 2024

The CPX11 and CPX21 instance types are both shared vCPU just that they are AMD and therefore more expensive:

autobase/console/db/migrations/20240520144338_2.0.0_initial_scheme_setup.sql

Lines 295 to 296 in 03157f7

('hetzner', 'Small Size', 'CPX11', 2, 2, 0.007, 5.180, '€', '2024-07-21'),
('hetzner', 'Small Size', 'CPX21', 3, 4, 0.010, 8.980, '€', '2024-07-21'),

https://www.hetzner.com/cloud/
image

As suggested by @schonert in #835 (comment), it makes sense to list the instance pricing in USD to aid comparison to all the bigger (way more expensive!) US-centric cloud providers ...

image

With your permission, can I update the migration lines to USD?
Won't affect any current users of v2.0.0 but will help any newer people going forward. 💭

nelsonic added a commit to nelsonic/autobase that referenced this issue Dec 9, 2024
@nelsonic
Update Hetzner instances in 20240520144338_2.0.0_initial_scheme_setup…
73c99b8 
….sql from EUR to USD ref: vitabaks#834 (comment)
@nelsonic
Copy link
Contributor Author

nelsonic commented Dec 9, 2024

Updated in https://github.com/vitabaks/autobase/pull/835/files 🤞

@nelsonic
Copy link
Contributor Author

nelsonic commented Dec 9, 2024 •
edited
Loading

The only storage that is listed in EUR is Hetzner:

autobase/console/db/migrations/20240520144338_2.0.0_initial_scheme_setup.sql

Line 354 in 03157f7

('hetzner', 'ssd', 'SSD Block Storage (Max throughput: N/A MiB/s, Max IOPS: N/A)', 10, 10000, 0.052, '€', true, '2024-05-15');

Going to update to USD to make comparison between cloud providers easier.

nelsonic added a commit to nelsonic/autobase that referenced this issue Dec 9, 2024
@nelsonic
Update Hetzner cloud_volumes from EUR to USD in 20240520144338_2.0.0_…
a922869 
…initial_scheme_setup.sql ref: vitabaks#834 (comment)
nelsonic added a commit to nelsonic/autobase that referenced this issue Dec 10, 2024
@nelsonic
Revert changes in 20240520144338_2.0.0_initial_scheme_setup.sql ref v…
e442c24 
…itabaks#835 (comment) instead these are updates in 2.1 vitabaks#834
@nelsonic
Copy link
Contributor Author

Added all the Hetzner Cloud instance types via: #835 ✅
Also addresses #784 👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Hetzner: Add shared vCPU instance types; EUR -> USD nelsonic/autobase
2 participants
@nelsonic @vitabaks