UpCloud Premium 1 vCPU / 2 GB
Server
-
ProviderUpCloud
-
PlanPremium 1 vCPU / 2 GB
-
LocationNew York #1
-
vCPU1
-
RAM2 GB
-
Storage25 GB NVMe
-
NetworkUnknown
-
OS image01000000-0000-4000-8000-000030240200
-
TriggerScheduled
-
Queued atOct 7, 2026, 17:53:00 UTC
Referral link. If you sign up through it, I may get paid.
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,692 | Skipped | Geekbench Browser |
Multi-core was skipped because Geekbench 7 needs about 2.1 GB of free memory to run 1 thread, and this server didn't have that much. Single-core needs much less, so it still ran.
Scores from different Geekbench versions aren't comparable with each other. Charts only use Geekbench 7.
Geekbench 7 workloads
| Workload | Single-core | Multi-core |
|---|---|---|
| File Compression |
1,802
|
Single-core only |
| Navigation |
1,328
|
Single-core only |
| HTML5 Browser |
1,449
|
Single-core only |
| PDF Viewer |
1,840
|
Single-core only |
| Photo Library |
1,976
|
Single-core only |
| Clang |
1,339
|
Single-core only |
| Text Processing |
1,390
|
Single-core only |
| Asset Compression |
1,876
|
Single-core only |
| HDR |
1,893
|
Single-core only |
| Photo Editor |
2,751
|
Single-core only |
| Ray Tracer |
1,128
|
Single-core only |
| Structure from Motion |
1,823
|
Single-core only |
| Game Physics |
1,549
|
Single-core only |
| Video Encoder |
1,714
|
Single-core only |
| Audio Encoder |
1,900
|
Single-core only |
| Video Player |
1,894
|
Single-core only |
Rank among the 53 runs with Geekbench 7 workload scores. Bars are relative to the best run. Geekbench doesn't run every workload multi-core, so some rows only have a single-core score.
Memory, TLS and scheduler
Memory bandwidth (STREAM)
| Test | Result | Runs | Spread |
|---|---|---|---|
| Copy higher is better | 37.2 GB/s | 3 | 7.04% |
| Scale higher is better | 36.2 GB/s | 3 | 8.14% |
| Add higher is better | 35.6 GB/s | 3 | 6.05% |
| Triad higher is better | 35.9 GB/s | 3 | 5.45% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
TLS and crypto (OpenSSL)
| Test | Result | Runs | Spread |
|---|---|---|---|
| RSA 4096 signs higher is better | 735/s | 3 | 1.75% |
| RSA 4096 verifies higher is better | 19,162/s | 3 | 2.64% |
| SHA-256 higher is better | 1.08 GB/s | 3 | 1.9% |
| AES-256-GCM higher is better | 16.5 GB/s | 3 | 6.93% |
| ChaCha20-Poly1305 higher is better | 5.22 GB/s | 3 | 1.4% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Scheduler latency (schbench)
| Test | Result | Runs | Spread |
|---|---|---|---|
| Request latency, median lower is better | 3.58 ms | 3 | 2.72% |
| Requests per second, 90th percentile higher is better | 284/s | 3 | 0.203% |
| Request latency, 99.9th percentile lower is better | 10.2 ms | 3 | 57.2% |
| Requests per second, average higher is better | 270/s | 3 | 2.55% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 78.9 MB/s (20,191 IOPS) | 79.1 MB/s (20,244 IOPS) | 158 MB/s (40,435 IOPS) |
| 64K | 376.4 MB/s (6,022 IOPS) | 378.4 MB/s (6,053 IOPS) | 754.7 MB/s (12,075 IOPS) |
| 512K | 381.5 MB/s (762 IOPS) | 401.7 MB/s (803 IOPS) | 783.2 MB/s (1,565 IOPS) |
| 1M | 377.6 MB/s (377 IOPS) | 402.7 MB/s (402 IOPS) | 780.3 MB/s (779 IOPS) |
fio random read and write, 50/50, run by YABS against the boot disk.
Network
IPv4 transfer speed
| Target | Protocol | Send | Receive |
|---|---|---|---|
| Clouvider, London, UK (10G) | IPv4 | 862 Mbps | 940 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 944 Mbps | 1.02 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 443 Mbps | 857 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 790 Mbps | 1.02 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.07 Gbps | 1.07 Gbps |
Public iperf3 servers vary in capacity and availability. Compare a target only with itself over time.
Datastores
PostgreSQL
fsync speed (pg_test_fsync)
| Method | Operations per second | Time per operation |
|---|---|---|
| One 8 kB write | ||
| open_datasync | 4,751 | 0.211 ms |
| fdatasync | 4,028 | 0.248 ms |
| fsync | 3,243 | 0.308 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 3,598 | 0.278 ms |
| Two 8 kB writes | ||
| open_datasync | 2,421 | 0.413 ms |
| fdatasync | 3,747 | 0.267 ms |
| fsync | 2,404 | 0.416 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,348 | 0.742 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 2,501 | 0.4 ms |
| 2 * 8kB open_sync writes | 1,377 | 0.726 ms |
| 4 * 4kB open_sync writes | 773 | 1.29 ms |
| 8 * 2kB open_sync writes | 356 | 2.81 ms |
| 16 * 1kB open_sync writes | 180 | 5.57 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 1,807 | 0.553 ms |
| write, close, fsync | 2,514 | 0.398 ms |
| Non-synced 8 kB writes | ||
| write | 2,239,807 | 0 ms |
pg_test_fsync against the Docker volume Postgres keeps its data on. fdatasync is Linux's default wal_sync_method.
pgbench at scale 10
| Workload | Clients | Transactions/s | Median | p95 | p99 | p99.9 | Failed |
|---|---|---|---|---|---|---|---|
| Read/write (TPC-B like) | 1 | 2,182 | 0.384 ms | 0.771 ms | 1.45 ms | 8.08 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,823 | 1.34 ms | 3.25 ms | 6.25 ms | 25.5 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,247 | 7.02 ms | 26.6 ms | 49.7 ms | 102 ms | 0 |
| Read only | 1 | 70,801 | 0.014 ms | 0.019 ms | 0.026 ms | 0.059 ms | 0 |
| Read only | 8 | 61,015 | 0.117 ms | 0.218 ms | 0.265 ms | 0.738 ms | 0 |
| Read only | 32 | 54,578 | 0.498 ms | 0.798 ms | 1.44 ms | 2.39 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.26 s. 60 s per run, prepared statements. Latency comes from sampled transaction logs, and p99.9 is left out when fewer than 1,000 were sampled.
pgbench at scale 100
| Workload | Clients | Transactions/s | Median | p95 | p99 | p99.9 | Failed |
|---|---|---|---|---|---|---|---|
| Read/write (TPC-B like) | 1 | 1,525 | 0.529 ms | 1.06 ms | 2.85 ms | 22.8 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,421 | 1.73 ms | 4.68 ms | 14.8 ms | 53.2 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,132 | 8.66 ms | 17.7 ms | 38.6 ms | 74 ms | 0 |
| Read only | 1 | 11,752 | 0.054 ms | 0.199 ms | 0.484 ms | 1.53 ms | 0 |
| Read only | 8 | 35,373 | 0.173 ms | 0.47 ms | 0.961 ms | 2.1 ms | 0 |
| Read only | 32 | 24,035 | 0.933 ms | 2.65 ms | 4.21 ms | 7.14 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 14.9 s. 60 s per run, prepared statements. Latency comes from sampled transaction logs, and p99.9 is left out when fewer than 1,000 were sampled.
MySQL
sysbench OLTP
| Workload | Threads | Transactions/s | Queries/s | Median | p95 | p99 | Errors |
|---|---|---|---|---|---|---|---|
| Read/write | 1 | 357 | 7,145 | 2.26 ms | 4.49 ms | 12.3 ms | 0 |
| Read/write | 8 | 684 | 13,689 | 10.5 ms | 20 ms | 39.7 ms | 0 |
| Read/write | 32 | 669 | 13,372 | 43.4 ms | 83 ms | 115 ms | 0 |
| Read only | 1 | 2,085 | 33,368 | 0.456 ms | 0.654 ms | 1.04 ms | 0 |
| Read only | 8 | 1,792 | 28,668 | 4.33 ms | 5.77 ms | 7.17 ms | 0 |
| Read only | 32 | 1,191 | 19,051 | 26.2 ms | 35.6 ms | 41.1 ms | 0 |
10 tables of 100,000 rows, loaded in 14.4 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 98,032 | 89,119 | 0.655 ms | 1.11 ms | 2.34 ms |
| 1:1 set:get | 95,710 | 47,855 | 0.671 ms | 1.13 ms | 2.34 ms |
1,000,000 keys of 32 bytes. 64 connections over 1 thread, 60 s per ratio.
Web frameworks
| Framework | Fortunes req/s | Single query req/s | JSON req/s | Fortunes p99 at 256 connections |
|---|---|---|---|---|
| Next.js | The results arrived but couldn't be read, so no numbers are shown. | |||
| Express | The results arrived but couldn't be read, so no numbers are shown. | |||
| Fastify | The results arrived but couldn't be read, so no numbers are shown. | |||
| NestJS | The results arrived but couldn't be read, so no numbers are shown. | |||
| Nuxt | The results arrived but couldn't be read, so no numbers are shown. | |||
| FastAPI | The results arrived but couldn't be read, so no numbers are shown. | |||
| Django | The results arrived but couldn't be read, so no numbers are shown. | |||
| Rails | The results arrived but couldn't be read, so no numbers are shown. | |||
| Laravel | The results arrived but couldn't be read, so no numbers are shown. | |||
| Symfony | The results arrived but couldn't be read, so no numbers are shown. | |||
WooCommerce
Page mix
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Home page | 1.05 | 1.46 s | 1.62 s | 1.65 s | 0% |
| Shop page | 1.05 | 1.87 s | 2.14 s | 2.37 s | 0% |
| Category page | 1.05 | 1.51 s | 1.94 s | 2.04 s | 0% |
| Product page | 1.05 | 1.4 s | 1.77 s | 1.81 s | 0% |
| Product search | 1.05 | 1.28 s | 1.67 s | 1.82 s | 0% |
| 32 virtual users | |||||
| Home page | 1.36 | 5.15 s | 5.73 s | 6.16 s | 0% |
| Shop page | 1.19 | 6.88 s | 8.44 s | 8.49 s | 0% |
| Category page | 0.907 | 6 s | 7.05 s | 7.38 s | 0% |
| Product page | 0.907 | 5.27 s | 6.32 s | 6.42 s | 0% |
| Product search | 0.907 | 5.13 s | 5.94 s | 6.09 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 1.78 | 1.58 s | 2.11 s | 2.33 s | 0% |
| Cart | 1.78 | 1.36 s | 1.72 s | 2.01 s | 0% |
| Checkout | 1.78 | 1.16 s | 1.56 s | 1.78 s | 0% |
| 32 virtual users | |||||
| Add to cart | 1.92 | 5.56 s | 7.08 s | 7.27 s | 0% |
| Cart | 1.92 | 5.99 s | 6.96 s | 7.19 s | 0% |
| Checkout | 1.92 | 4.86 s | 5.52 s | 5.77 s | 0% |
k6 with a fixed number of virtual users, 66 to 71 s per level. The error rate counts responses that weren't a 200.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 1 | 1 |
| CPU | Shared vCPU | 3.1% of busy CPU time stolen |
| RAM | 2 GB | 1.8 GiB |
| Storage | 25 GB NVMe | 24.5 GiB |
| Architecture | x86_64 | x86_64 |
| Virtualization | KVM | KVM |
Guests usually report slightly less RAM and disk than advertised because of kernel reservations and filesystem overhead.
Detected hardware
- CPU model
- AMD EPYC 9575F 64-Core Processor
- CPU cores
- 1
- CPU frequency
- 3295 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- No
- RAM reported
- 1.8 GiB
- Swap reported
- 0 MiB
- Disk reported
- 24.5 GiB
- Virtualization reported
- KVM
- CPU steal
- 3.1% of busy CPU time stolen
- Distro
- Ubuntu 24.04.4 LTS
- Kernel
- 6.8.0-137-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- Yes
Advertised at test time
- Plan
- Premium 1 vCPU / 2 GB
- Product line
- Premium
- Location
- New York #1
- vCPU
- 1 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 25 GB NVMe
- Virtualization
- KVM
- Network
- Unknown
- Transfer
- 1.02 TB
- Port 25
- Unknown
- Monthly price at test time
- €12.00 EUR
- Hourly price at test time
- €0.018 EUR
- YABS version
- v2026-09-20
- Ran at
- Oct 7, 2026, 17:57:13 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 7, 2026, 17:53:00 UTC
- Server created
- Oct 7, 2026, 17:55:12 UTC
- First update from the server
- Oct 7, 2026, 17:55:12 UTC
- Completed
- Oct 7, 2026, 19:08:00 UTC
- Server deleted
- Oct 7, 2026, 19:08:00 UTC
- Cost of this run
- €0.022 EUR
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading output.
This party closed at . It's read only now.
Reconnecting. Hang tight.