Posted in VPS Showdown

VPS Showdown – July 2024 – DigitalOcean vs. Linode vs. Vultr

This post is old news – Get fresh benchmarks at VPS Showdown (daily updates!)

While not as perfect as I would like, this month we'll continue with comparing plans with AMD processors from DigitalOcean, Linode, and Vultr.

Pricing ranges from $5 to $7, and while each instance has an AMD processor, there is still a mix of what you may end up with. DigitalOcean still isn't very transparent with their offering, obscuring the actual processor with a generic placeholder.

All instances are running the latest LTS release of Ubuntu, and I've spun up 3 instances with each provider. Of course, the results are averaged where it makes the most sense.

Overview - DigitalOcean vs. Linode vs. Vultr

Version
Linux Distro Ubuntu 24.04 LTS
Kernel Version 6.8.0
MySQL Version 8.0.37
Redis Version 7.0.15
DigitalOcean Linode Vultr
Location New York 1 Newark, NJ New York (NJ)
Monthly Price $7/month $5/month $6/month
Hourly Price $0.01/hour $0.0075/hour $0.009/hour
RAM 1 GB 1 GB 1 GB
CPU 1 Core 1 Core 1 Core
Storage 25 GB 25 GB 25 GB
Storage Type NVMe SSD NVMe
Transfer 1 TB 1 TB 1 TB
Transfer Overage $0.01/GB $0.01/GB $0.01/GB
Backups $1.4/month $2/month $1.2/month

CPU Info

Model Name
DigitalOcean - All Instances DO-Premium-AMD
Linode - Instance #1 AMD EPYC 7642 48-Core Processor
Linode - Instance #2 AMD EPYC 7713 64-Core Processor
Linode - Instance #3 AMD EPYC 7713 64-Core Processor
Vultr - Instance #1 AMD EPYC-Milan Processor
Vultr - Instance #2 AMD EPYC-Rome Processor
Vultr - Instance #3 AMD EPYC-Milan Processor
DigitalOcean Linode Vultr
CPU MHz 1,996.25 2,100.00 2,832.08
Cache Size (KB) 512.00 512.00 512.00
BogoMips 2,661.67 2,866.67 4,333.33

CPU

DigitalOcean Linode Vultr
Events per Second 1,333.94 2,877.22 3,219.65
Minimum (ms) 0.64 0.37 0.25
Average (ms) 0.75 0.41 0.31
Maximum (ms) 3.37 4.34 16.62

Memory

Read

DigitalOcean Linode Vultr
Ops per Second 4,390,045.26 5,386,780.70 4,346,224.83
Minimum (ms) 0.00 0.00 0.00
Average (ms) 0.00 0.00 0.00
Maximum (ms) 0.58 3.06 10.73

Write

DigitalOcean Linode Vultr
Ops per Second 4,332,418.85 5,378,927.34 4,276,949.03
Minimum (ms) 0.00 0.00 0.00
Average (ms) 0.00 0.00 0.00
Maximum (ms) 0.34 2.78 21.31

File I/O

DigitalOcean Linode Vultr
Reads per Second 1,338.78 2,753.55 1,401.49
Writes per Second 892.52 1,835.68 934.33
Fsyncs per Second 2,860.84 5,879.77 2,996.44
Minimum (ms) 0.00 0.00 0.00
Average (ms) 0.20 0.10 0.21
Maximum (ms) 12.58 9.50 37.59

MySQL

Read Only

DigitalOcean Linode Vultr
Transactions per Second 4,062.67 6,218.33 4,336.67
Queries per Second 65,002.67 99,493.33 69,386.67
Minimum (ms) 1.51 1.21 1.09
Average (ms) 2.47 1.65 2.41
Maximum (ms) 18.34 19.03 62.40

Write Only

DigitalOcean Linode Vultr
Transactions per Second 1,793.67 3,969.00 2,043.00
Queries per Second 10,762.00 23,814.00 12,258.00
Minimum (ms) 1.96 1.12 1.54
Average (ms) 5.60 2.58 7.34
Maximum (ms) 54.57 35.50 70.68

Read Write

DigitalOcean Linode Vultr
Transactions per Second 1,060.33 2,079.00 1,242.67
Queries per Second 21,206.67 41,580.00 24,853.33
Minimum (ms) 4.52 2.68 3.62
Average (ms) 9.53 4.94 10.57
Maximum (ms) 52.36 26.65 65.91

Redis

DigitalOcean Linode Vultr
PING_INLINE 29,700.80 45,979.56 32,104.56
PING_MBULK 27,511.12 46,237.21 32,141.48
SET 30,270.98 44,801.67 31,164.65
GET 31,855.76 44,608.93 28,590.99
INCR 31,612.29 44,639.14 27,237.30
LPUSH 30,145.69 43,066.53 29,820.29
RPUSH 29,625.89 44,312.28 31,420.83
LPOP 29,079.21 44,880.43 31,285.98
RPOP 28,477.13 46,003.19 32,139.83
SADD 31,072.77 47,503.48 31,257.73
HSET 30,892.96 46,016.45 31,019.08
SPOP 31,544.95 45,788.99 27,426.15
LRANGE_100 (first 100 elements) 19,968.73 29,491.14 22,334.52
LRANGE_300 (first 300 elements) 11,472.20 16,961.34 12,288.00
LRANGE_500 (first 500 elements) 7,263.38 11,649.21 7,779.99
LRANGE_600 (first 600 elements) 6,701.63 10,030.43 7,350.11
MSET (10 keys) 28,136.23 41,529.36 29,748.23

Conclusion

Not much really changed this month with Linode out performing in most categories. Small observation would be that last month one of the Linode instances was 32-core, and the other two were 64-core. This month we had a mix of 48-core and 64-core. I'm curious if we'll see that trend in the direction of 64-core being the only processor we see until the next generation lands.

As always, I highly recommend you do your own tests and definitely spin up multiple instances before you make a commitment. Last thing you want is your brand new project running on last year's hardware.

If you have found these posts informative and helpful in searching for a new hosting provider, please consider using one of the links below when signing up:

:wq


Like this drivel? There's a whole RSS feed of it, or subscribe via email.