Hetzner deprecated my CX11 server plan

After logging into my Hetzner account, I was met with a message informing me that my current cloud server plan was being deprecated. I could either choose to keep my existing server plan or rescale it. In my experience, this approach is usually a disguised upsell attempt, but thankfully not so with Hetzner.

Hetzner - Deprecated server message

CX11 is deprecated. It’s possible to migrate this server to another server plan.

I’ve been on Hetzner’s CX11 cloud server plan for almost two years, and it has more than enough juice to run this little blog. However, I do not like running anything with the label deprecated attached to it so I will look to migrate to another server plan.

Same price, twice the resources

Let me see if I get this right. By rescaling the server to the new CX22 plan the price remains the same, but I get 2 VPCU, 4GB RAM, and 40GB storage. Seems like one of those too-good-to-be-true offers, but was unable to find any small print suggesting otherwise.

Hetzner - Rescale server

Using the rescale feature to migrate from CX11 to the new CX22 cloud server plan.

Migrating to the CX22 cloud server plan

The rescale process ran for a couple of minutes and afterward, the server booted right back up. Everything seems to be running as expected and journalctl doesn’t list any errors. Viewing the server from Hetzner’s control panel confirmed that the migration had been completed successfully:

Hetzner - CX22 cloud server

Post-migration to the CX22 server plan. Same monthly price, but more resources.

Is this a sponsored post?

Heh, maybe this post reads like a cheesy advert, but there will never be any sponsored posts on this blog. Either way, I always recommend that people do their research instead of taking advice from some random person on the Internet.

I’m just very pleased with the amount of bang for the buck I’m getting with Hetzner. Their features and stability are also on par (or better) with comparable cloud providers. In my two years with Hetnzer, I’ve not had a single service interruption. Additionally, German privacy laws are really strict so that’s also a plus in my book.

I’ll go out on a limb and add my affiliate Hetzner link as a personal recommendation. If you sign up using the link, you’ll get €⁠20 in cloud credits. If you spend at least €⁠10 with Hetzner, I’ll receive €⁠10 in cloud credits.

Sign up using this link to receive €⁠20 in cloud credits with Hetzner.
*Available for new customers only

Nench.sh benchmark results

I performed a benchmark check before and after the rescaling to verify that there was not an obvious degradation in performance after the migration to the new server plan. Here are the results:

CX11

-------------------------------------------------
 nench.sh v2019.07.20 -- https://git.io/nench.sh
 benchmark timestamp:    2024-06-22 08:49:02 UTC
-------------------------------------------------

Processor:    Intel Xeon Processor (Skylake, IBRS)
CPU cores:    1
Frequency:    2100.000 MHz
RAM:          1.9Gi
Swap:         -
Kernel:       Linux 6.9.5-arch1-1 x86_64

Disks:
sda   19.1G  SSD

CPU: SHA256-hashing 500 MB
    1.831 seconds
CPU: bzip2-compressing 500 MB
    6.317 seconds
CPU: AES-encrypting 500 MB
    1.327 seconds

ioping: seek rate
    min/avg/max/mdev = 111.2 us / 260.8 us / 7.87 ms / 105.1 us
ioping: sequential read speed
    generated 7.67 k requests in 5.00 s, 1.87 GiB, 1.53 k iops, 383.4 MiB/s

dd: sequential write speed
    1st run:    892.64 MiB/s
    2nd run:    839.23 MiB/s
    3rd run:    908.85 MiB/s
    average:    880.24 MiB/s

-------------------------------------------------

CX22

-------------------------------------------------
 nench.sh v2019.07.20 -- https://git.io/nench.sh
 benchmark timestamp:    2024-06-22 09:16:52 UTC
-------------------------------------------------

Processor:    Intel Xeon Processor (Skylake, IBRS, no TSX)
CPU cores:    2
Frequency:    2294.614 MHz
RAM:          3.7Gi
Swap:         -
Kernel:       Linux 6.9.5-arch1-1 x86_64

Disks:
sda   38.1G  SSD

CPU: SHA256-hashing 500 MB
    1.780 seconds
CPU: bzip2-compressing 500 MB
    6.501 seconds
CPU: AES-encrypting 500 MB
    1.532 seconds

ioping: seek rate
    min/avg/max/mdev = 80.9 us / 201.4 us / 2.98 ms / 77.2 us
ioping: sequential read speed
    generated 10.5 k requests in 5.00 s, 2.57 GiB, 2.10 k iops, 525.4 MiB/s

dd: sequential write speed
    1st run:    1049.04 MiB/s
    2nd run:    1144.41 MiB/s
    3rd run:    1144.41 MiB/s
    average:    1112.62 MiB/s

-------------------------------------------------

The new server plan is an improvement in most contexts, except for CPU-intensive tasks.

If you feel there is any reason why I should not recommend Hetzner as a cloud service provider then please get in touch.

Related