UpCloud Starter 4 vCPU / 8 GB
Server
-
ProviderUpCloud
-
PlanStarter 4 vCPU / 8 GB
-
LocationSan Jose #1
-
vCPU4
-
RAM8 GB
-
Storage40 GB
-
NetworkUnknown
-
OS image01000000-0000-4000-8000-000030240200
-
TriggerScheduled
-
Queued atOct 18, 2026, 03:59:00 UTC
Referral link. If you sign up through it, I may get paid. How this works
Latest runs of this plan
- Chicago #1 Oct 18, 2026 1,196
- New York #1 Oct 17, 2026 1,276
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,309 | 4,580 | Geekbench Browser |
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,450
|
4,324
|
| Navigation |
1,523
|
Single-core only |
| HTML5 Browser |
1,185
|
Single-core only |
| PDF Viewer |
1,392
|
Single-core only |
| Photo Library |
1,171
|
4,467
|
| Clang |
1,236
|
4,887
|
| Text Processing |
1,141
|
4,076
|
| Asset Compression |
1,274
|
5,062
|
| HDR |
1,047
|
3,379
|
| Photo Editor |
1,435
|
5,388
|
| Ray Tracer |
1,381
|
5,457
|
| Structure from Motion |
1,452
|
Single-core only |
| Game Physics |
1,363
|
Single-core only |
| Video Encoder |
1,250
|
Single-core only |
| Audio Encoder |
1,333
|
Single-core only |
| Video Player |
1,420
|
Single-core only |
Rank among the 241 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 | 78 GB/s | 3 | 19.6% |
| Scale higher is better | 63.1 GB/s | 3 | 14% |
| Add higher is better | 62.7 GB/s | 3 | 19% |
| Triad higher is better | 64.8 GB/s | 3 | 19.9% |
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 | 942/s | 3 | 0.209% |
| RSA 4096 verifies higher is better | 61,411/s | 3 | 0.125% |
| SHA-256 higher is better | 2.82 GB/s | 3 | 0.235% |
| AES-256-GCM higher is better | 14.3 GB/s | 3 | 0.0693% |
| ChaCha20-Poly1305 higher is better | 7.25 GB/s | 3 | 0.0411% |
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 | 4.03 ms | 3 | 0.115% |
| Requests per second, 90th percentile higher is better | 968/s | 3 | 0.119% |
| Request latency, 99.9th percentile lower is better | 8.08 ms | 3 | 4.97% |
| Requests per second, average higher is better | 956/s | 3 | 0.285% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 38.9 MB/s (9,966 IOPS) | 39 MB/s (9,990 IOPS) | 78 MB/s (19,956 IOPS) |
| 64K | 399 MB/s (6,383 IOPS) | 401 MB/s (6,416 IOPS) | 800 MB/s (12,799 IOPS) |
| 512K | 382.5 MB/s (764 IOPS) | 402.8 MB/s (805 IOPS) | 785.3 MB/s (1,569 IOPS) |
| 1M | 379.5 MB/s (379 IOPS) | 404.8 MB/s (404 IOPS) | 784.4 MB/s (783 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 | 1.06 Gbps | 1.08 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.06 Gbps | 1.07 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 1.05 Gbps | 976 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.16 Gbps | 1.16 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.12 Gbps | 1.1 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 | 3,365 | 0.297 ms |
| fdatasync | 3,543 | 0.282 ms |
| fsync | 1,460 | 0.685 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,728 | 0.579 ms |
| Two 8 kB writes | ||
| open_datasync | 1,856 | 0.539 ms |
| fdatasync | 2,848 | 0.351 ms |
| fsync | 1,649 | 0.607 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 810 | 1.23 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 1,578 | 0.634 ms |
| 2 * 8kB open_sync writes | 716 | 1.4 ms |
| 4 * 4kB open_sync writes | 393 | 2.55 ms |
| 8 * 2kB open_sync writes | 219 | 4.58 ms |
| 16 * 1kB open_sync writes | 104 | 9.6 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 1,484 | 0.674 ms |
| write, close, fsync | 1,487 | 0.672 ms |
| Non-synced 8 kB writes | ||
| write | 543,007 | 0.002 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 | 1,388 | 0.664 ms | 0.927 ms | 1.69 ms | 4.82 ms | 0 |
| Read/write (TPC-B like) | 8 | 5,490 | 1.19 ms | 2.75 ms | 4.7 ms | 13.3 ms | 0 |
| Read/write (TPC-B like) | 32 | 6,155 | 3.66 ms | 13.7 ms | 24.6 ms | 49 ms | 0 |
| Read only | 1 | 22,939 | 0.042 ms | 0.055 ms | 0.065 ms | 0.09 ms | 0 |
| Read only | 8 | 85,239 | 0.086 ms | 0.152 ms | 0.186 ms | 0.25 ms | 0 |
| Read only | 32 | 103,180 | 0.266 ms | 0.442 ms | 0.536 ms | 0.749 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.42 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,145 | 0.78 ms | 1.06 ms | 2.33 ms | 10.6 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,172 | 1.31 ms | 2.39 ms | 10.4 ms | 90.4 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,547 | 3.57 ms | 7.64 ms | 89.5 ms | 107 ms | 0 |
| Read only | 1 | 18,224 | 0.05 ms | 0.068 ms | 0.082 ms | 0.129 ms | 0 |
| Read only | 8 | 69,557 | 0.106 ms | 0.185 ms | 0.229 ms | 0.554 ms | 0 |
| Read only | 32 | 79,838 | 0.36 ms | 0.556 ms | 0.691 ms | 1.23 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 16.6 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 | 285 | 5,699 | 3.13 ms | 4.57 ms | 9.73 ms | 0 |
| Read/write | 8 | 1,060 | 21,194 | 6.32 ms | 11.7 ms | 51.9 ms | 0 |
| Read/write | 32 | 1,517 | 30,345 | 20 ms | 36.2 ms | 56.8 ms | 0 |
| Read only | 1 | 886 | 14,179 | 1.1 ms | 1.32 ms | 1.61 ms | 0 |
| Read only | 8 | 3,496 | 55,930 | 2.22 ms | 3.13 ms | 4.25 ms | 0 |
| Read only | 32 | 3,380 | 54,082 | 9.39 ms | 11.7 ms | 13.5 ms | 0 |
10 tables of 100,000 rows, loaded in 5.8 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 61,329 | 55,753 | 1.02 ms | 2.02 ms | 2.16 ms |
| 1:1 set:get | 60,851 | 30,425 | 1.03 ms | 2.03 ms | 2.22 ms |
1,000,000 keys of 32 bytes. 64 connections over 4 threads, 60 s per ratio.
Web frameworks
| Framework | Fortunes req/s | Single query req/s | JSON req/s | Fortunes p99 at 256 connections |
|---|---|---|---|---|
| Next.js nextjs | 1,376 | 4,976 | 7,173 | 304 ms |
| Express express-postgresjs | 16,671 | 23,131 | 59,732 | 32.9 ms |
| Fastify fastify-postgres | 16,517 | 24,018 | 59,841 | 35.2 ms |
| NestJS nestjs | 10,290 | 11,826 | 41,230 | 45.6 ms |
| Nuxt nuxt | 14,589 | 22,413 | 61,337 | 43.6 ms |
| FastAPI fastapi | 8,020 | 9,800 | 34,329 | 139 ms |
| Django django-postgresql | 4,017 | 4,573 | 10,867 | 125 ms |
| Rails rails | 6,194 | 8,252 | 32,213 | 86.3 ms |
| Laravel laravel | 1,751 | 1,848 | 3,658 | 158 ms |
| Symfony symfony | 2,202 | 2,432 | 6,811 | 124 ms |
Peak requests per second across the 64 and 256 connection levels, measured with wrk. Each test has to pass the TechEmpower response checks first, or it's marked invalid.
Web apps
WooCommerce
Page mix
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Home page | 4.9 | 326 ms | 429 ms | 470 ms | 0% |
| Shop page | 4.9 | 429 ms | 551 ms | 580 ms | 0% |
| Category page | 4.9 | 281 ms | 440 ms | 537 ms | 0% |
| Product page | 4.9 | 311 ms | 413 ms | 449 ms | 0% |
| Product search | 4.9 | 270 ms | 358 ms | 390 ms | 0% |
| 32 virtual users | |||||
| Home page | 4.71 | 1.28 s | 1.48 s | 1.58 s | 0% |
| Shop page | 4.71 | 1.67 s | 1.9 s | 1.96 s | 0% |
| Category page | 4.71 | 1.32 s | 1.77 s | 1.89 s | 0% |
| Product page | 4.71 | 1.25 s | 1.43 s | 1.49 s | 0% |
| Product search | 4.71 | 1.15 s | 1.31 s | 1.35 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 9.37 | 338 ms | 437 ms | 474 ms | 0% |
| Cart | 9.37 | 292 ms | 377 ms | 411 ms | 0% |
| Checkout | 9.37 | 231 ms | 299 ms | 326 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 9.06 | 1.29 s | 1.54 s | 1.6 s | 0% |
| Cart | 9.06 | 1.21 s | 1.41 s | 1.48 s | 0% |
| Checkout | 9.06 | 1 s | 1.16 s | 1.22 s | 0% |
k6 with a fixed number of virtual users, 61 to 63 s per level. The error rate counts responses that weren't a 200.
Discourse
Signed in
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Topic page | 2.6 | 173 ms | 186 ms | 388 ms | 0% |
| Topic JSON | 1.31 | 88.7 ms | 102 ms | 112 ms | 0% |
| Home page | 1.31 | 156 ms | 169 ms | 258 ms | 0% |
| Categories page | 0.663 | 182 ms | 194 ms | 199 ms | 0% |
| User activity page | 0.646 | 106 ms | 149 ms | 200 ms | 0% |
| 4 virtual users | |||||
| Topic page | 8.88 | 199 ms | 251 ms | 501 ms | 0% |
| Topic JSON | 4.43 | 103 ms | 120 ms | 174 ms | 0% |
| Home page | 4.43 | 180 ms | 218 ms | 454 ms | 0% |
| Categories page | 2.23 | 209 ms | 254 ms | 516 ms | 0% |
| User activity page | 2.22 | 127 ms | 201 ms | 285 ms | 0% |
| 16 virtual users | |||||
| Topic page | 8.52 | 776 ms | 971 ms | 1.32 s | 0% |
| Topic JSON | 4.28 | 576 ms | 729 ms | 865 ms | 0% |
| Home page | 4.26 | 736 ms | 966 ms | 1.21 s | 0% |
| Categories page | 2.15 | 786 ms | 1.02 s | 1.43 s | 0% |
| User activity page | 2.11 | 640 ms | 786 ms | 893 ms | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 177 | 22.5 ms | 44.1 ms | 61.4 ms | 0% |
| Topic JSON | 88.6 | 20.8 ms | 41.8 ms | 63.2 ms | 0% |
| Home page | 88.6 | 22.8 ms | 43.7 ms | 62.9 ms | 0% |
| Categories page | 44.3 | 22.2 ms | 43.4 ms | 64.5 ms | 0% |
| User activity page | 44.3 | 133 ms | 174 ms | 289 ms | 0% |
k6 with a fixed number of virtual users, 60 to 61 s per level, after a 21 s warmup. The error rate counts responses that weren't a 200. Discourse ran with 8 app workers and 2048 MB of Postgres shared buffers, what its installer picks for a 8 GB box. Its installer adds no swap on a box this big. The container peaked at 2,823 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 10.8 | 27.4 ms | 29.5 ms | 33.8 ms | 0% |
| Post page | 27 | 13.9 ms | 15.9 ms | 21.4 ms | 0% |
| Tag page | 5.41 | 18.5 ms | 20.5 ms | 25.7 ms | 0% |
| Author page | 5.41 | 18.4 ms | 20.2 ms | 24.1 ms | 0% |
| RSS feed | 5.41 | 20.2 ms | 22.1 ms | 26.8 ms | 0% |
| 4 virtual users | |||||
| Home page | 12.7 | 83.7 ms | 105 ms | 112 ms | 0% |
| Post page | 31.6 | 58.1 ms | 78.1 ms | 87 ms | 0% |
| Tag page | 6.34 | 53.5 ms | 71.2 ms | 80.7 ms | 0% |
| Author page | 6.32 | 53.7 ms | 70.9 ms | 79 ms | 0% |
| RSS feed | 6.31 | 59.6 ms | 78.3 ms | 86.3 ms | 0% |
| 16 virtual users | |||||
| Home page | 12.6 | 330 ms | 378 ms | 396 ms | 0% |
| Post page | 31.5 | 266 ms | 316 ms | 340 ms | 0% |
| Tag page | 6.28 | 183 ms | 224 ms | 238 ms | 0% |
| Author page | 6.31 | 180 ms | 225 ms | 244 ms | 0% |
| RSS feed | 6.31 | 187 ms | 228 ms | 244 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 5.81 | 26.5 ms | 29.3 ms | 33.7 ms | 0% |
| Post editor | 17.5 | 9.33 ms | 11.5 ms | 13.5 ms | 0% |
| Saving a draft | 17.4 | 25.4 ms | 29.8 ms | 44.3 ms | 0% |
| Member list | 5.81 | 33.1 ms | 37.7 ms | 45 ms | 0% |
| 4 virtual users | |||||
| Post list | 7.41 | 33.1 ms | 38 ms | 40.1 ms | 0% |
| Post editor | 22.3 | 15 ms | 19.2 ms | 21.1 ms | 0% |
| Saving a draft | 22.3 | 136 ms | 167 ms | 176 ms | 0% |
| Member list | 7.44 | 42.4 ms | 46.2 ms | 48.4 ms | 0% |
k6 with a fixed number of virtual users, 60 s per level, after a 20 s warmup. The error rate counts responses that weren't a 200. Ghost ran the way its ghost-docker setup runs it: one Node process, and MySQL with its stock 128 MB buffer pool. Memory peaked with Ghost at 531 MB and MySQL at 625 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 2.03 | 65.8 ms | 69.7 ms | 71.3 ms | 0% |
| Blog index | 2.03 | 219 ms | 229 ms | 233 ms | 0% |
| Blog post | 6.05 | 21.5 ms | 33.1 ms | 34.1 ms | 0% |
| Bread page | 6.07 | 23.8 ms | 25.6 ms | 26.2 ms | 0% |
| Location page | 2.03 | 22.7 ms | 24.2 ms | 25.3 ms | 0% |
| Site search | 2.01 | 37.9 ms | 61.3 ms | 63 ms | 0% |
| 4 virtual users | |||||
| Home page | 3.19 | 179 ms | 269 ms | 296 ms | 0% |
| Blog index | 3.24 | 611 ms | 885 ms | 995 ms | 0% |
| Blog post | 9.62 | 49.2 ms | 89.5 ms | 125 ms | 0% |
| Bread page | 9.63 | 54.7 ms | 86 ms | 99 ms | 0% |
| Location page | 3.24 | 47.9 ms | 78.4 ms | 154 ms | 0% |
| Site search | 3.21 | 77.2 ms | 171 ms | 201 ms | 0% |
| 16 virtual users | |||||
| Home page | 3.5 | 525 ms | 648 ms | 696 ms | 0% |
| Blog index | 3.55 | 1.43 s | 1.65 s | 1.7 s | 0% |
| Blog post | 10.5 | 297 ms | 440 ms | 541 ms | 0% |
| Bread page | 10.5 | 304 ms | 446 ms | 540 ms | 0% |
| Location page | 3.52 | 306 ms | 445 ms | 505 ms | 0% |
| Site search | 3.5 | 358 ms | 551 ms | 668 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.744 | 71.8 ms | 77.2 ms | 193 ms | 0% |
| Page explorer | 1.5 | 321 ms | 362 ms | 449 ms | 0% |
| Page editor | 2.23 | 151 ms | 194 ms | 287 ms | 0% |
| Image library | 0.744 | 55.8 ms | 64.8 ms | 473 ms | 0% |
| Admin page search | 0.744 | 29.9 ms | 66.1 ms | 67.8 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.22 | 240 ms | 487 ms | 634 ms | 0% |
| Page explorer | 2.49 | 666 ms | 1.18 s | 1.56 s | 0% |
| Page editor | 3.76 | 377 ms | 720 ms | 831 ms | 0% |
| Image library | 1.27 | 176 ms | 452 ms | 500 ms | 0% |
| Admin page search | 1.22 | 91.4 ms | 214 ms | 300 ms | 0% |
k6 with a fixed number of virtual users, 60 to 61 s per level, after a 21 s warmup. The error rate counts responses that weren't a 200. Wagtail ran the way bakerydemo ships it: uWSGI with 2 workers of 4 threads each, whatever the box, and Postgres and Redis on stock settings. Memory peaked with Wagtail at 299 MB, Postgres at 152 MB, and Redis at 25 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 4 | 4 |
| CPU | Shared vCPU | 0% of busy CPU time stolen |
| RAM | 8 GB | 7.7 GiB |
| Storage | 40 GB | 39.3 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 7542 32-Core Processor
- CPU cores
- 4
- CPU frequency
- 2895 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- No
- RAM reported
- 7.7 GiB
- Swap reported
- 0 MiB
- Disk reported
- 39.3 GiB
- Virtualization reported
- KVM
- CPU steal
- 0% 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
- Starter 4 vCPU / 8 GB
- Product line
- Starter
- Location
- San Jose #1
- vCPU
- 4 shared vCPU
- Architecture
- x86_64
- RAM
- 8 GB
- Storage
- 40 GB
- Virtualization
- KVM
- Network
- Unknown
- Transfer
- 2.05 TB
- Port 25
- Unknown
- Monthly price at test time
- €24.00 EUR
- Hourly price at test time
- €0.036 EUR
- YABS version
- v2026-09-20
- Ran at
- Oct 18, 2026, 04:00:37 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 18, 2026, 03:59:00 UTC
- Server created
- Oct 18, 2026, 04:00:15 UTC
- First update from the server
- Oct 18, 2026, 04:00:15 UTC
- Completed
- Oct 18, 2026, 05:35:04 UTC
- Server deleted
- Oct 18, 2026, 05:35:04 UTC
- Cost of this run
- €0.057 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 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.