Kamatera 2B 2GB 40GB
Server
-
ProviderKamatera
-
Plan2B 2GB 40GB
-
LocationAtlanta
-
vCPU2
-
RAM2 GB
-
Storage40 GB SSD
-
NetworkUnknown
-
OS imageubuntu_server_24.04_64-bit
-
TriggerScheduled
-
Queued atOct 14, 2026, 16:31:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,326 | Skipped | Geekbench Browser |
Multi-core was skipped because Geekbench 7 needs about 3.1 GB of free memory to run 2 threads, 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,368
|
Single-core only |
| Navigation |
1,287
|
Single-core only |
| HTML5 Browser |
1,231
|
Single-core only |
| PDF Viewer |
1,407
|
Single-core only |
| Photo Library |
1,366
|
Single-core only |
| Clang |
1,233
|
Single-core only |
| Text Processing |
1,350
|
Single-core only |
| Asset Compression |
1,540
|
Single-core only |
| HDR |
1,216
|
Single-core only |
| Photo Editor |
1,537
|
Single-core only |
| Ray Tracer |
1,224
|
Single-core only |
| Structure from Motion |
1,507
|
Single-core only |
| Game Physics |
1,226
|
Single-core only |
| Video Encoder |
1,200
|
Single-core only |
| Audio Encoder |
1,257
|
Single-core only |
| Video Player |
1,339
|
Single-core only |
Rank among the 170 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 | 42.4 GB/s | 3 | 1.11% |
| Scale higher is better | 25.1 GB/s | 3 | 0.789% |
| Add higher is better | 30.8 GB/s | 3 | 0.361% |
| Triad higher is better | 30.7 GB/s | 3 | 0.875% |
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 | 1,024/s | 3 | 1.02% |
| RSA 4096 verifies higher is better | 28,433/s | 3 | 1.65% |
| SHA-256 higher is better | 1.64 GB/s | 3 | 2.26% |
| AES-256-GCM higher is better | 22.4 GB/s | 3 | 4.3% |
| ChaCha20-Poly1305 higher is better | 6.84 GB/s | 3 | 1.17% |
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 | 2.5 ms | 3 | 0.64% |
| Requests per second, 90th percentile higher is better | 756/s | 3 | 1.25% |
| Request latency, 99.9th percentile lower is better | 5.85 ms | 3 | 0.987% |
| Requests per second, average higher is better | 701/s | 3 | 2% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 181.9 MB/s (46,558 IOPS) | 182.3 MB/s (46,681 IOPS) | 364.2 MB/s (93,239 IOPS) |
| 64K | 1.67 GB/s (27,371 IOPS) | 1.68 GB/s (27,515 IOPS) | 3.35 GB/s (54,886 IOPS) |
| 512K | 4.59 GB/s (9,410 IOPS) | 4.84 GB/s (9,910 IOPS) | 9.43 GB/s (19,320 IOPS) |
| 1M | 4.66 GB/s (4,775 IOPS) | 4.97 GB/s (5,093 IOPS) | 9.64 GB/s (9,868 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.99 Gbps | 2.55 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 2.02 Gbps | 2.49 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 685 Mbps | 1.07 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 3.15 Gbps | 4.51 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 8.2 Gbps | 5.45 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,903 | 0.145 ms |
| fdatasync | 6,704 | 0.149 ms |
| fsync | 5,197 | 0.192 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 5,645 | 0.177 ms |
| Two 8 kB writes | ||
| open_datasync | 3,530 | 0.283 ms |
| fdatasync | 6,706 | 0.149 ms |
| fsync | 4,668 | 0.214 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 2,585 | 0.387 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 4,928 | 0.203 ms |
| 2 * 8kB open_sync writes | 2,462 | 0.406 ms |
| 4 * 4kB open_sync writes | 1,169 | 0.856 ms |
| 8 * 2kB open_sync writes | 642 | 1.56 ms |
| 16 * 1kB open_sync writes | 329 | 3.04 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 4,821 | 0.207 ms |
| write, close, fsync | 4,452 | 0.225 ms |
| Non-synced 8 kB writes | ||
| write | 1,531,015 | 0.001 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,480 | 0.314 ms | 0.735 ms | 1.63 ms | 4.2 ms | 0 |
| Read/write (TPC-B like) | 8 | 5,736 | 1.16 ms | 2.79 ms | 5.2 ms | 16 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,612 | 4.25 ms | 14.3 ms | 24.3 ms | 46.4 ms | 0 |
| Read only | 1 | 26,464 | 0.04 ms | 0.06 ms | 0.098 ms | 0.214 ms | 0 |
| Read only | 8 | 76,296 | 0.094 ms | 0.165 ms | 0.211 ms | 0.446 ms | 0 |
| Read only | 32 | 73,076 | 0.371 ms | 0.722 ms | 1.03 ms | 1.74 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.13 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,274 | 0.698 ms | 1.28 ms | 2.96 ms | 6.2 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,915 | 1.38 ms | 3.37 ms | 6.04 ms | 11 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,931 | 4.95 ms | 8.86 ms | 12.2 ms | 18.4 ms | 0 |
| Read only | 1 | 8,251 | 0.102 ms | 0.274 ms | 0.512 ms | 2.27 ms | 0 |
| Read only | 8 | 42,973 | 0.141 ms | 0.418 ms | 0.651 ms | 2.21 ms | 0 |
| Read only | 32 | 40,984 | 0.639 ms | 1.45 ms | 2.26 ms | 3.86 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 11.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 | 448 | 8,962 | 2 ms | 3.62 ms | 6.21 ms | 0 |
| Read/write | 8 | 1,139 | 22,786 | 6.55 ms | 11.7 ms | 15.5 ms | 0 |
| Read/write | 32 | 1,246 | 24,922 | 24.4 ms | 43.4 ms | 56.8 ms | 0 |
| Read only | 1 | 874 | 13,991 | 1.08 ms | 1.55 ms | 1.89 ms | 0 |
| Read only | 8 | 2,700 | 43,203 | 2.81 ms | 4.1 ms | 5 ms | 0 |
| Read only | 32 | 2,183 | 34,929 | 14.5 ms | 21.9 ms | 25.3 ms | 0 |
10 tables of 100,000 rows, loaded in 7.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 | 96,974 | 88,158 | 0.423 ms | 2.46 ms | 4.22 ms |
| 1:1 set:get | 96,525 | 48,262 | 0.423 ms | 2.46 ms | 4.26 ms |
1,000,000 keys of 32 bytes. 64 connections over 2 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 | 406 | 1,630 | 2,010 | 846 ms |
| Express express-postgresjs | 7,515 | 10,494 | 53,798 | 61.3 ms |
| Fastify fastify-postgres | 7,471 | 12,796 | 66,914 | 61.8 ms |
| NestJS nestjs | 6,470 | 6,838 | 37,976 | 90.8 ms |
| Nuxt nuxt | 6,372 | 11,749 | 50,209 | 77.4 ms |
| FastAPI fastapi | 4,160 | 5,764 | 23,852 | 262 ms |
| Django django-postgresql | 1,701 | 1,976 | 3,646 | 259 ms |
| Rails rails | 2,256 | 3,493 | 23,983 | 182 ms |
| Laravel laravel | 744 | 805 | 1,339 | 383 ms |
| Symfony symfony | 891 | 1,007 | 2,895 | 338 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 | 2.18 | 729 ms | 843 ms | 877 ms | 0% |
| Shop page | 2.18 | 999 ms | 1.15 s | 1.2 s | 0% |
| Category page | 2.18 | 591 ms | 1.03 s | 1.1 s | 0% |
| Product page | 2.18 | 667 ms | 781 ms | 803 ms | 0% |
| Product search | 2.18 | 573 ms | 694 ms | 725 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.26 | 2.65 s | 3.03 s | 3.36 s | 0% |
| Shop page | 2.26 | 3.65 s | 4.18 s | 4.4 s | 0% |
| Category page | 2.26 | 3.11 s | 3.81 s | 3.96 s | 0% |
| Product page | 2.12 | 2.66 s | 2.87 s | 2.95 s | 0% |
| Product search | 1.81 | 2.42 s | 2.66 s | 2.72 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.25 | 769 ms | 870 ms | 909 ms | 0% |
| Cart | 4.25 | 601 ms | 678 ms | 701 ms | 0% |
| Checkout | 4.25 | 460 ms | 527 ms | 551 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.18 | 2.59 s | 3.24 s | 3.44 s | 0% |
| Cart | 4.18 | 2.72 s | 3.13 s | 3.28 s | 0% |
| Checkout | 4.18 | 2.08 s | 2.41 s | 2.66 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.
Discourse
Signed in
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Topic page | 2.12 | 211 ms | 273 ms | 437 ms | 0% |
| Topic JSON | 1.06 | 104 ms | 124 ms | 144 ms | 0% |
| Home page | 1.08 | 185 ms | 345 ms | 471 ms | 0% |
| Categories page | 0.53 | 215 ms | 258 ms | 314 ms | 0% |
| User activity page | 0.53 | 130 ms | 176 ms | 273 ms | 0% |
| 4 virtual users | |||||
| Topic page | 3.69 | 469 ms | 792 ms | 1.03 s | 0% |
| Topic JSON | 1.85 | 235 ms | 396 ms | 436 ms | 0% |
| Home page | 1.84 | 413 ms | 624 ms | 1.07 s | 0% |
| Categories page | 0.943 | 513 ms | 667 ms | 986 ms | 0% |
| User activity page | 0.91 | 304 ms | 419 ms | 604 ms | 0% |
| 16 virtual users | |||||
| Topic page | 3.63 | 1.51 s | 2.02 s | 2.15 s | 0% |
| Topic JSON | 1.86 | 1.31 s | 1.75 s | 1.87 s | 0% |
| Home page | 1.88 | 1.45 s | 2 s | 2.31 s | 0% |
| Categories page | 0.923 | 1.49 s | 1.85 s | 2.18 s | 0% |
| User activity page | 0.907 | 1.32 s | 1.74 s | 1.91 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 75.2 | 58.1 ms | 143 ms | 181 ms | 0% |
| Topic JSON | 37.6 | 59.4 ms | 145 ms | 188 ms | 0% |
| Home page | 37.7 | 62.1 ms | 150 ms | 185 ms | 0% |
| Categories page | 18.8 | 54.4 ms | 137 ms | 187 ms | 0% |
| User activity page | 18.9 | 190 ms | 292 ms | 413 ms | 0% |
k6 with a fixed number of virtual users, 60 to 62 s per level, after a 21 s warmup. The error rate counts responses that weren't a 200. Discourse ran with 4 app workers and 256 MB of Postgres shared buffers, what its installer picks for a 2 GB box. It added a 2 GB swapfile first, the way its installer does, and used up to 477 MB of it. The container peaked at 1,428 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 8 | 35.4 ms | 45.2 ms | 54.3 ms | 0% |
| Post page | 20 | 19.1 ms | 24.3 ms | 32.7 ms | 0% |
| Tag page | 4 | 22.7 ms | 28.8 ms | 35.2 ms | 0% |
| Author page | 4 | 23.7 ms | 29.5 ms | 31.7 ms | 0% |
| RSS feed | 3.98 | 26.2 ms | 33.9 ms | 44.5 ms | 0% |
| 4 virtual users | |||||
| Home page | 10.4 | 102 ms | 149 ms | 175 ms | 0% |
| Post page | 25.9 | 69.8 ms | 103 ms | 131 ms | 0% |
| Tag page | 5.19 | 61.4 ms | 93.8 ms | 134 ms | 0% |
| Author page | 5.18 | 65.6 ms | 92.9 ms | 118 ms | 0% |
| RSS feed | 5.18 | 64.6 ms | 96.4 ms | 123 ms | 0% |
| 16 virtual users | |||||
| Home page | 11 | 357 ms | 470 ms | 497 ms | 0% |
| Post page | 27.4 | 303 ms | 403 ms | 442 ms | 0% |
| Tag page | 5.47 | 193 ms | 276 ms | 307 ms | 0% |
| Author page | 5.49 | 189 ms | 274 ms | 317 ms | 0% |
| RSS feed | 5.47 | 203 ms | 291 ms | 314 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 4.45 | 31.2 ms | 44.6 ms | 62.5 ms | 0% |
| Post editor | 13.4 | 13.5 ms | 18.3 ms | 25.9 ms | 0% |
| Saving a draft | 13.4 | 33.8 ms | 44.2 ms | 67.5 ms | 0% |
| Member list | 4.47 | 34.7 ms | 48.7 ms | 51.9 ms | 0% |
| 4 virtual users | |||||
| Post list | 5.8 | 42.9 ms | 55.3 ms | 96.8 ms | 0% |
| Post editor | 17.5 | 21.7 ms | 29.5 ms | 51 ms | 0% |
| Saving a draft | 17.5 | 171 ms | 235 ms | 279 ms | 0% |
| Member list | 5.86 | 45.7 ms | 58.8 ms | 110 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 361 MB and MySQL at 569 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.58 | 82.4 ms | 97.1 ms | 110 ms | 0% |
| Blog index | 1.58 | 286 ms | 314 ms | 347 ms | 0% |
| Blog post | 4.7 | 26.6 ms | 40 ms | 51.9 ms | 0% |
| Bread page | 4.72 | 29.5 ms | 35.9 ms | 42.1 ms | 0% |
| Location page | 1.58 | 27.7 ms | 32.6 ms | 36 ms | 0% |
| Site search | 1.56 | 45.9 ms | 78.5 ms | 84.2 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.52 | 211 ms | 315 ms | 366 ms | 0% |
| Blog index | 2.55 | 755 ms | 1.03 s | 1.14 s | 0% |
| Blog post | 7.6 | 62.5 ms | 104 ms | 134 ms | 0% |
| Bread page | 7.6 | 72.1 ms | 110 ms | 128 ms | 0% |
| Location page | 2.57 | 66.2 ms | 102 ms | 111 ms | 0% |
| Site search | 2.53 | 104 ms | 207 ms | 251 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.23 | 824 ms | 1.1 s | 1.34 s | 0% |
| Blog index | 2.3 | 2.18 s | 2.59 s | 2.85 s | 0% |
| Blog post | 6.68 | 476 ms | 727 ms | 868 ms | 0% |
| Bread page | 6.76 | 468 ms | 742 ms | 1 s | 0% |
| Location page | 2.25 | 447 ms | 712 ms | 949 ms | 0% |
| Site search | 2.23 | 574 ms | 914 ms | 947 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.728 | 89.4 ms | 111 ms | 123 ms | 0% |
| Page explorer | 1.46 | 318 ms | 397 ms | 484 ms | 0% |
| Page editor | 2.19 | 152 ms | 200 ms | 254 ms | 0% |
| Image library | 0.728 | 60.1 ms | 78.1 ms | 546 ms | 0% |
| Admin page search | 0.728 | 38.4 ms | 77.2 ms | 129 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.2 | 280 ms | 449 ms | 517 ms | 0% |
| Page explorer | 2.41 | 786 ms | 1.29 s | 1.7 s | 0% |
| Page editor | 3.58 | 346 ms | 679 ms | 779 ms | 0% |
| Image library | 1.2 | 195 ms | 451 ms | 556 ms | 0% |
| Admin page search | 1.2 | 117 ms | 272 ms | 299 ms | 0% |
k6 with a fixed number of virtual users, 60 to 61 s per level, after a 20 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 296 MB, Postgres at 175 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 40 GB SSD | 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
- Intel Xeon Processor (SapphireRapids)
- CPU cores
- 2
- CPU frequency
- 2700 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- Yes
- RAM reported
- 1.9 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.5 LTS
- Kernel
- 6.8.0-139-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- No
Advertised at test time
- Plan
- 2B 2GB 40GB
- Product line
- Type B General Purpose
- Location
- Atlanta
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 40 GB SSD
- Virtualization
- KVM
- Network
- Unknown
- Transfer
- 5 TB
- Port 25
- Unknown
- Monthly price at test time
- $28.00
- Hourly price at test time
- $0.038
- YABS version
- v2026-09-20
- Ran at
- Oct 14, 2026, 16:33:23 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 14, 2026, 16:31:00 UTC
- First update from the server
- Oct 14, 2026, 16:33:20 UTC
- Completed
- Oct 14, 2026, 18:05:00 UTC
- Server deleted
- Oct 14, 2026, 18:05:00 UTC
- Cost of this run
- $0.060
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.