# UpCloud Premium 1 vCPU / 1 GB [San Jose #1](https://rackcensus.com/locations/san-jose-vps-benchmarks "Every provider in San Jose") Benchmark complete Finished Oct 7, 2026 Geekbench 7 single-core Skipped Geekbench 7 multi-core Skipped Disk 4K IOPS 40,090 fio random read and write, 50/50 Monthly price at test time €6.00 EUR Same price today ## Server [UpCloud](https://rackcensus.com/vps-providers/upcloud-benchmarks)[Premium 1 vCPU / 1 GB](https://rackcensus.com/plans/9tjgtd-upcloud-premium-1-vcpu-1-gb-benchmarks?location=us-sjo1) - Provider UpCloud - Plan Premium 1 vCPU / 1 GB - Location San Jose #1 - vCPU 1 - RAM 1 GB - Storage 25 GB NVMe - Network Unknown - OS image 01000000-0000-4000-8000-000030240200 - Trigger Scheduled - Queued at Oct 7, 2026, 19:16:00 UTC [Visit UpCloud](https://rackcensus.com/go/upcloud) Referral link. If you sign up through it, I may get paid. [Skip the referral](https://rackcensus.com/go/upcloud/direct)[How this works](https://rackcensus.com/transparency#referrals-heading) ## Latest runs of this plan - [Frankfurt #1 Oct 9, 2026](https://rackcensus.com/benchmarks/djcoyk-upcloud-premium-1-vcpu-1-gb-de-fra1-benchmark)Skipped - [New York #1 Oct 6, 2026](https://rackcensus.com/benchmarks/h6n0js-upcloud-premium-1-vcpu-1-gb-us-nyc1-benchmark)Skipped [Full history of this plan](https://rackcensus.com/plans/9tjgtd-upcloud-premium-1-vcpu-1-gb-benchmarks/history) ## CPU Geekbench was skipped because this plan has less than 2 GB of RAM, which isn't enough for Geekbench 7 to run without swap. ## Memory, TLS and scheduler ### Memory bandwidth (STREAM) | Test | Result | Runs | Spread | | --- | --- | --- | --- | | Copy higher is better | 45.3 GB/s | 3 | 1.6% | | Scale higher is better | 38.3 GB/s | 3 | 1.28% | | Add higher is better | 40.2 GB/s | 3 | 3.41% | | Triad higher is better | 40.5 GB/s | 3 | 2.43% | 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 | 731/s | 3 | 1.28% | | RSA 4096 verifies higher is better | 18,953/s | 3 | 6.02% | | SHA-256 higher is better | 1.1 GB/s | 3 | 1.61% | | AES-256-GCM higher is better | 17.6 GB/s | 3 | 3.06% | | ChaCha20-Poly1305 higher is better | 5.12 GB/s | 3 | 1% | 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.43 ms | 3 | 0.587% | | Requests per second, 90th percentile higher is better | 296/s | 3 | 1.56% | | Request latency, 99.9th percentile lower is better | 6.68 ms | 3 | 4.29% | | Requests per second, average higher is better | 279/s | 3 | 0.7% | Average of 3 runs. Spread is the standard deviation as a share of the average. ## Disk | Block size | Read | Write | Total | | --- | --- | --- | --- | | 4K | 78.2 MB/s (20,019 IOPS) | 78.4 MB/s (20,071 IOPS) | 156.6 MB/s (40,090 IOPS) | | 64K | 398.6 MB/s (6,378 IOPS) | 400.7 MB/s (6,411 IOPS) | 799.4 MB/s (12,789 IOPS) | | 512K | 381.5 MB/s (763 IOPS) | 401.8 MB/s (803 IOPS) | 783.3 MB/s (1,566 IOPS) | | 1M | 376.7 MB/s (376 IOPS) | 401.7 MB/s (401 IOPS) | 778.4 MB/s (777 IOPS) | fio random read and write, 50/50, run by YABS against the boot disk. ## Network ### IPv4 transfer speed Loading... | Target | Protocol | Send | Receive | | --- | --- | --- | --- | | Clouvider, London, UK (10G) | IPv4 | 942 Mbps | 981 Mbps | | Eranium, Amsterdam, NL (100G) | IPv4 | 963 Mbps | 978 Mbps | | Leaseweb, Singapore, SG (10G) | IPv4 | 906 Mbps | 819 Mbps | | Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.06 Gbps | 1.07 Gbps | | Leaseweb, NYC, NY, US (10G) | IPv4 | 1.03 Gbps | 1.01 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 | 6,257 | 0.16 ms | | fdatasync | 6,485 | 0.154 ms | | fsync | 5,088 | 0.197 ms | | fsync\_writethrough | Not supported here | n/a | | open\_sync | 5,156 | 0.194 ms | | Two 8 kB writes | | --- | | open\_datasync | 3,082 | 0.324 ms | | fdatasync | 5,669 | 0.176 ms | | fsync | 3,871 | 0.258 ms | | fsync\_writethrough | Not supported here | n/a | | open\_sync | 2,490 | 0.402 ms | | open\_sync at different write sizes | | --- | | 1 \* 16kB open\_sync write | 4,337 | 0.231 ms | | 2 \* 8kB open\_sync writes | 2,475 | 0.404 ms | | 4 \* 4kB open\_sync writes | 1,300 | 0.769 ms | | 8 \* 2kB open\_sync writes | 689 | 1.45 ms | | 16 \* 1kB open\_sync writes | 318 | 3.14 ms | | fsync on a non-write descriptor | | --- | | write, fsync, close | 4,737 | 0.211 ms | | write, close, fsync | 4,905 | 0.204 ms | | Non-synced 8 kB writes | | --- | | write | 2,493,273 | 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 | 3,172 | 0.283 ms | 0.455 ms | 0.762 ms | 4.04 ms | 0 | | Read/write (TPC-B like) | 8 | 6,294 | 1.1 ms | 2.26 ms | 3.67 ms | 19.1 ms | 0 | | Read/write (TPC-B like) | 32 | 4,708 | 5.07 ms | 16.6 ms | 30.4 ms | 57.4 ms | 0 | | Read only | 1 | 75,580 | 0.012 ms | 0.019 ms | 0.029 ms | 0.061 ms | 0 | | Read only | 8 | 63,960 | 0.11 ms | 0.211 ms | 0.261 ms | 0.607 ms | 0 | | Read only | 32 | 57,141 | 0.491 ms | 0.679 ms | 0.941 ms | 2 ms | 0 | Scale 10 (1,000,000 accounts), loaded in 1.31 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,730 | 0.5 ms | 0.857 ms | 1.98 ms | 11.2 ms | 0 | | Read/write (TPC-B like) | 8 | 4,478 | 1.44 ms | 3.01 ms | 5.16 ms | 47 ms | 0 | | Read/write (TPC-B like) | 32 | 3,943 | 6.94 ms | 12.6 ms | 28.7 ms | 67.1 ms | 0 | | Read only | 1 | 6,622 | 0.133 ms | 0.243 ms | 0.603 ms | 1.86 ms | 0 | | Read only | 8 | 26,016 | 0.276 ms | 0.516 ms | 1.28 ms | 2.1 ms | 0 | | Read only | 32 | 25,115 | 1.01 ms | 2.1 ms | 3.15 ms | 5.6 ms | 0 | Scale 100 (10,000,000 accounts), loaded in 14.8 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 Failed: ran out of memory with 1 oom kills, sysbench oltp\_read\_write with 32 threads exited 1: DISTINCT c FROM sbtest5 WHERE id BETWEEN ? AND ? ORDER BY c' FATAL: mysql\_stmt\_execute() returned error 2013 (Lost connection to MySQL server during query) for query 'UPDATE sbtest10 SET c=? WHERE id=?' (last message repeated 23 times) FATAL: `thread\_run' function failed: /usr/share/sysbench/oltp\_common.lua:469: SQL error, errno = 2013, state = 'HY000': Lost connection to MySQL server during query ### Redis #### memtier | Mix | Operations/s | Hits/s | Median | p99 | p99.9 | | --- | --- | --- | --- | --- | --- | | 1:10 set:get | 98,672 | 89,701 | 0.655 ms | 1.05 ms | 2.24 ms | | 1:1 set:get | 98,658 | 49,329 | 0.655 ms | 1.08 ms | 2.21 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.28 | 1.13 s | 1.57 s | 1.65 s | 0% | | Shop page | 1.28 | 1.51 s | 1.86 s | 1.95 s | 0% | | Category page | 1.28 | 1.25 s | 1.68 s | 1.74 s | 0% | | Product page | 1.28 | 1.13 s | 1.39 s | 1.46 s | 0% | | Product search | 1.28 | 1.05 s | 1.33 s | 1.36 s | 0% | | 32 virtual users | | --- | | Home page | 1.36 | 4.25 s | 6.02 s | 6.1 s | 0% | | Shop page | 1.36 | 6.08 s | 6.99 s | 7.1 s | 0% | | Category page | 1.36 | 5.51 s | 6.64 s | 6.9 s | 0% | | Product page | 1.1 | 4.76 s | 5.17 s | 5.2 s | 0% | | Product search | 0.906 | 4.49 s | 5.03 s | 5.07 s | 0% | #### Cart and checkout | Step | Requests/s | Median | p95 | p99 | Error rate | | --- | --- | --- | --- | --- | --- | | 8 virtual users | | --- | | Add to cart | 2.37 | 1.12 s | 1.53 s | 1.7 s | 0% | | Cart | 2.37 | 1.13 s | 1.53 s | 1.62 s | 0% | | Checkout | 2.37 | 883 ms | 1.17 s | 1.29 s | 0% | | 32 virtual users | | --- | | Add to cart | 2.65 | 4.01 s | 5.1 s | 5.26 s | 0% | | Cart | 2.65 | 4.34 s | 5.11 s | 5.28 s | 0% | | Checkout | 2.65 | 3.5 s | 4.01 s | 4.28 s | 0% | k6 with a fixed number of virtual users, 63 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 | 2.9% of busy CPU time stolen | | RAM | 1 GB | 848 MiB | | 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:** 848 MiB **Swap reported:** 0 MiB **Disk reported:** 24.5 GiB **Virtualization reported:** KVM **CPU steal:** 2.9% 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 / 1 GB **Product line:** Premium **Location:** San Jose #1 **vCPU:** 1 shared vCPU **Architecture:** x86\_64 **RAM:** 1 GB **Storage:** 25 GB NVMe **Virtualization:** KVM **Network:** Unknown **Transfer:** 512 GB **Port 25:** Unknown **Monthly price at test time:** €6.00 EUR **Hourly price at test time:** €0.0089 EUR **YABS version:** v2026-09-20 **Ran at:** Oct 7, 2026, 19:20:17 UTC **Parser version:** 5 ## Run timeline **Queued:** Oct 7, 2026, 19:16:00 UTC **First update from the server:** Oct 7, 2026, 19:18:16 UTC **Completed:** Oct 7, 2026, 20:23:00 UTC **Server deleted:** Oct 7, 2026, 20:23:00 UTC **Cost of this run:** €0.0100 EUR Tests 34 of 35 done Live output 699 lines Setup 1 cores, 847.5 MiB RAM 4 of 4Done Disk (fio) 164 MB/s at 4k, 816 MB/s at 1m 5 of 5Done Network, IPv4 (iperf3) Median 963 Mbit/s send, 981 Mbit/s receive 5 of 5Done Phoronix (memory, TLS, scheduler) 3 of 3Done Datastores 1 failed 4 of 5Some failed TestResultTimevs last run Postgres fsync fsync Passed 1m 29s Postgres scale 10 select\_only 32c 57,141 tps tps, select\_only 32c 6m 07s Postgres scale 100 select\_only 32c 25,115 tps tps, select\_only 32c 6m 19s MySQL sysbench oltp\_read\_write 32t Stopped ran out of memory with 1 oom kills, sysbench oltp\_read\_write with 32 threads exited 1: DISTINCT c FROM sbtest5 WHERE id BETWEEN ? AND ? ORDER BY c' FATAL: mysql\_stmt\_execute() returned error 2013 (Lost connection to MySQL server during query) for query 'UPDATE sbtest10 SET c=? WHERE id=?' (last message repeated 23 times) FATAL: `thread\_run' function failed: /usr/share/sysbench/oltp\_common.lua:469: SQL error, errno = 2013, state = 'HY000': Lost connection to MySQL server during query 2m 55s Redis memtier 1:1 98,658 ops/s ops, 1:1 2m 17s Web frameworks 12 of 12Done Finish Results saved 1 of 1Done Watch party 0 watching This party closed at 20:23 UTC. It's read only now. ## Watch party Loading the party