-
-
Notifications
You must be signed in to change notification settings - Fork 420
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
Hetzner server types #784
Comments
Hi. Yes, we can add other types. Which ones are you interested in? As far as I recall, all available server types are included, except for shared CPUs, which were not added because they are not recommended for production use. Additionally, you can modify or add types in the database of your console installation. |
I was interested in beefier shared CPUs. So CX32 and above, CPX31 and above, and CAX21 and above. Not under the impression that they are not recommended for production?
Arhh great point! |
I see that only 6 types of servers are present with a dedicated CPU: All of them are in the console database.
Servers with shared vCPUs are not suitable for production databases because they do not guarantee consistent performance. Virtual CPUs on these servers are shared among multiple virtual machines, which can lead to unpredictable delays and reduced speed under heavy workloads. This is particularly critical for databases, where steady access to resources is essential to ensure low-latency responses and stable performance under load.
Yes, we could add all available types (with the exception of arm, since its support has not yet been implemented), but in this case it is necessary to explicitly mark the "Shared vCPU" types in the UI. |
This is awesome!
Would we be able to add more server types to the hetzner list? https://github.com/vitabaks/postgresql_cluster/blob/c9c9f02d0dd7991e3966f0e6c35dd4f3d3c45af0/console/db/migrations/20240520144338_2.0.0_initial_scheme_setup.sql#L295-L302
I could stitch together a PR - altho not sure if there's a good reason to limit it to these 8.
The text was updated successfully, but these errors were encountered: