Upcloud dev vps benchmark

This is 3 EUR VPS plan from UpCloud.

Basic System Information:
---------------------------------
Uptime     : 0 days, 0 hours, 1 minutes
Processor  : AMD EPYC 7542 32-Core Processor
CPU cores  : 1 @ 2894.560 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ❌ Disabled
RAM        : 864.4 MiB
Swap       : 0.0 KiB
Disk       : 9.8 GiB
Distro     : Debian GNU/Linux 13 (trixie)
Kernel     : 6.12.38+deb13-amd64
VM Type    : KVM
IPv4/IPv6  : ✔ Online / ✔ Online

IPv6 Network Information:
---------------------------------
ISP        : UpCloud Ltd
ASN        : AS202053 UpCloud Ltd
Location   : Madrid, Madrid (MD)
Country    : Spain

fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda2):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 39.85 MB/s    (9.9k) | 409.00 MB/s   (6.3k)
Write      | 39.95 MB/s    (9.9k) | 411.15 MB/s   (6.4k)
Total      | 79.80 MB/s   (19.9k) | 820.16 MB/s  (12.8k)
           |                      |
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 391.58 MB/s    (764) | 388.21 MB/s    (379)
Write      | 412.38 MB/s    (805) | 414.06 MB/s    (404)
Total      | 803.96 MB/s   (1.5k) | 802.27 MB/s    (783)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping
-----           | -----                     | ----            | ----            | ----
Clouvider       | London, UK (10G)          | 8.15 Gbits/sec  | 1.16 Gbits/sec  | 14.5 ms
Eranium         | Amsterdam, NL (100G)      | busy            | busy            | 7.51 ms
Uztelecom       | Tashkent, UZ (10G)        | 1.37 Gbits/sec  | 334 Mbits/sec   | 84.5 ms
Leaseweb        | Singapore, SG (10G)       | 1.22 Gbits/sec  | 986 Mbits/sec   | --
Clouvider       | Los Angeles, CA, US (10G) | 1.16 Gbits/sec  | 1.08 Gbits/sec  | 156 ms
Leaseweb        | NYC, NY, US (10G)         | 2.46 Gbits/sec  | 1.08 Gbits/sec  | 83.4 ms
Edgoo           | Sao Paulo, BR (1G)        | 1.08 Gbits/sec  | 705 Mbits/sec   | 199 ms

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping
-----           | -----                     | ----            | ----            | ----
Clouvider       | London, UK (10G)          | 8.09 Gbits/sec  | 1.16 Gbits/sec  | 14.5 ms
Eranium         | Amsterdam, NL (100G)      | 7.12 Gbits/sec  | 1.16 Gbits/sec  | 7.19 ms
Uztelecom       | Tashkent, UZ (10G)        | 1.19 Gbits/sec  | 1.09 Gbits/sec  | 84.4 ms
Leaseweb        | Singapore, SG (10G)       | 1.16 Gbits/sec  | 1.01 Gbits/sec  | 160 ms
Clouvider       | Los Angeles, CA, US (10G) | 1.15 Gbits/sec  | 1.07 Gbits/sec  | 155 ms
Leaseweb        | NYC, NY, US (10G)         | 2.50 Gbits/sec  | 1.05 Gbits/sec  | 83.5 ms
Edgoo           | Sao Paulo, BR (1G)        | 1.02 Gbits/sec  | 983 Mbits/sec   | 193 ms

Geekbench test failed and low memory was detected. Add at least 1GB of SWAP or use GB4 instead (higher compatibility with low memory systems).

Comments

Post a Comment

Popular posts from this blog

Email trifecta: SPF, DKIM, and DMARC with AWS SES

To be honest, based on my experiences, sending email is hard. Sometimes the email we expect goes to inbox, it is not. Internet is a weird place we love. For this reason, I am delegating email wroks to 3rd party, like AWS SES. But's also not like simple setup for using it. Whenever setup email on AWS SES, basically we need to setup: Create configuration set Verify domain ownership Setup correct SPF, DKIM, and DMARC Configuration set Think of a configuration set as a "sending profile" for your emails. By default, when you send an email with SES, it's like sending it into a black box. You know it was sent, but you don't know what happened next. Did it get delivered? Did it bounce? Did the user mark it as spam? A configuration set allows you to apply a specific set of rules and, most importantly, get detailed feedback on the outcome of your emails. For example: noreply email .  With noreply email , you're not expecting a reply, but you abso...
Read more

Setting Up AWS SES with Rails Action Mailer

Image
Sending emails isn't just about building infrastructure and software - the real challenge lies in ensuring your emails reach users' inboxes without being flagged as spam. In my experience with email SaaS providers, despite their premium pricing, emails often ended up in spam folders. Enter AWS Simple Email Service (SES). AWS SES offers a compelling solution with: Strong reputation and low spam scores Competitive pricing Flexible implementation (aws-ses-sdk or SMTP) Using AWS SES in us-west-1 region costs $0.10 per 1,000 emails. While the pricing model is complex (considering attachments and external network delivery), its pay-as-you-go structure works well for low-volume users. In my case, monthly costs never exceed $1, with a 100% delivery rate. Setup Process Important: New AWS SES accounts start in sandbox mode. You'll need to open a support ticket to upgrade to production status. While AWS provides aws-sdk-ses , I prefer using SMTP to...
Read more