Kamatera 2A 2GB 40GB
Server
-
ProviderKamatera
-
Plan2A 2GB 40GB
-
LocationAtlanta
-
vCPU2
-
RAM2 GB
-
Storage40 GB SSD
-
NetworkUnknown
-
OS imageubuntu_server_24.04_64-bit
-
TriggerScheduled
-
Queued atOct 12, 2026, 11:01:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,236 | 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,355
|
Single-core only |
| Navigation |
1,203
|
Single-core only |
| HTML5 Browser |
1,260
|
Single-core only |
| PDF Viewer |
1,368
|
Single-core only |
| Photo Library |
1,284
|
Single-core only |
| Clang |
1,103
|
Single-core only |
| Text Processing |
1,306
|
Single-core only |
| Asset Compression |
1,519
|
Single-core only |
| HDR |
1,204
|
Single-core only |
| Photo Editor |
1,004
|
Single-core only |
| Ray Tracer |
1,098
|
Single-core only |
| Structure from Motion |
1,482
|
Single-core only |
| Game Physics |
1,104
|
Single-core only |
| Video Encoder |
1,168
|
Single-core only |
| Audio Encoder |
1,227
|
Single-core only |
| Video Player |
1,206
|
Single-core only |
Rank among the 129 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 | 38.2 GB/s | 3 | 7.08% |
| Scale higher is better | 23.3 GB/s | 3 | 5.91% |
| Add higher is better | 28.4 GB/s | 3 | 6.04% |
| Triad higher is better | 28.2 GB/s | 3 | 7.79% |
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,006/s | 3 | 1.4% |
| RSA 4096 verifies higher is better | 27,756/s | 3 | 1.53% |
| SHA-256 higher is better | 1.57 GB/s | 3 | 3.48% |
| AES-256-GCM higher is better | 23.3 GB/s | 3 | 0.834% |
| ChaCha20-Poly1305 higher is better | 6.89 GB/s | 3 | 0.456% |
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.48 ms | 3 | 0.373% |
| Requests per second, 90th percentile higher is better | 766/s | 3 | 0.797% |
| Request latency, 99.9th percentile lower is better | 8.38 ms | 3 | 47.3% |
| Requests per second, average higher is better | 699/s | 3 | 2.14% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 197.9 MB/s (50,672 IOPS) | 198.5 MB/s (50,806 IOPS) | 396.4 MB/s (101,478 IOPS) |
| 64K | 1.74 GB/s (28,468 IOPS) | 1.75 GB/s (28,618 IOPS) | 3.48 GB/s (57,086 IOPS) |
| 512K | 4.22 GB/s (8,636 IOPS) | 4.44 GB/s (9,095 IOPS) | 8.66 GB/s (17,731 IOPS) |
| 1M | 4.73 GB/s (4,845 IOPS) | 5.05 GB/s (5,168 IOPS) | 9.78 GB/s (10,013 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.96 Gbps | 2.63 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.95 Gbps | 2.41 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 917 Mbps | 1.08 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.72 Gbps | 4.68 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 8.52 Gbps | 5.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 | 7,104 | 0.141 ms |
| fdatasync | 6,914 | 0.145 ms |
| fsync | 4,889 | 0.205 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 5,371 | 0.186 ms |
| Two 8 kB writes | ||
| open_datasync | 3,522 | 0.284 ms |
| fdatasync | 6,596 | 0.152 ms |
| fsync | 4,537 | 0.22 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 2,857 | 0.35 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 5,832 | 0.171 ms |
| 2 * 8kB open_sync writes | 2,932 | 0.341 ms |
| 4 * 4kB open_sync writes | 1,539 | 0.65 ms |
| 8 * 2kB open_sync writes | 729 | 1.37 ms |
| 16 * 1kB open_sync writes | 374 | 2.68 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 5,110 | 0.196 ms |
| write, close, fsync | 4,828 | 0.207 ms |
| Non-synced 8 kB writes | ||
| write | 1,659,314 | 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,463 | 0.332 ms | 0.718 ms | 1.63 ms | 4.04 ms | 0 |
| Read/write (TPC-B like) | 8 | 5,461 | 1.22 ms | 2.91 ms | 5.56 ms | 13.2 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,556 | 4.32 ms | 14.4 ms | 24.8 ms | 43 ms | 0 |
| Read only | 1 | 21,903 | 0.043 ms | 0.072 ms | 0.126 ms | 0.285 ms | 0 |
| Read only | 8 | 73,402 | 0.099 ms | 0.17 ms | 0.218 ms | 0.444 ms | 0 |
| Read only | 32 | 70,003 | 0.398 ms | 0.705 ms | 1.04 ms | 1.79 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.4 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,277 | 0.661 ms | 1.32 ms | 3.56 ms | 15.4 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,509 | 1.46 ms | 3.73 ms | 7.08 ms | 17 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,238 | 5.55 ms | 10.3 ms | 14.7 ms | 24.5 ms | 0 |
| Read only | 1 | 6,775 | 0.115 ms | 0.323 ms | 0.715 ms | 2.88 ms | 0 |
| Read only | 8 | 37,876 | 0.153 ms | 0.474 ms | 0.885 ms | 2.76 ms | 0 |
| Read only | 32 | 35,640 | 0.739 ms | 1.68 ms | 2.57 ms | 4.8 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 13.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
| Workload | Threads | Transactions/s | Queries/s | Median | p95 | p99 | Errors |
|---|---|---|---|---|---|---|---|
| Read/write | 1 | 451 | 9,018 | 2 ms | 3.43 ms | 6.1 ms | 0 |
| Read/write | 8 | 1,060 | 21,209 | 7.17 ms | 12.3 ms | 16.1 ms | 0 |
| Read/write | 32 | 1,104 | 22,072 | 27.7 ms | 49.2 ms | 66.8 ms | 0 |
| Read only | 1 | 814 | 13,027 | 1.16 ms | 1.73 ms | 2.15 ms | 0 |
| Read only | 8 | 2,465 | 39,439 | 3.25 ms | 4.82 ms | 6.43 ms | 0 |
| Read only | 32 | 2,111 | 33,775 | 14.5 ms | 21.1 ms | 25.3 ms | 0 |
10 tables of 100,000 rows, loaded in 7.3 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 94,831 | 86,209 | 0.407 ms | 2.54 ms | 4.38 ms |
| 1:1 set:get | 94,665 | 47,332 | 0.407 ms | 2.56 ms | 4.38 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 | 374 | 1,472 | 1,704 | 952 ms |
| Express express-postgresjs | 7,164 | 11,664 | 50,586 | 79.9 ms |
| Fastify fastify-postgres | 6,739 | 11,943 | 54,045 | 69.6 ms |
| NestJS nestjs | 5,686 | 5,841 | 34,852 | 106 ms |
| Nuxt nuxt | 5,955 | 11,479 | 47,588 | 98.3 ms |
| FastAPI fastapi | 3,560 | 5,170 | 22,461 | 258 ms |
| Django django-postgresql | 1,244 | 1,499 | 3,838 | 313 ms |
| Rails rails | 3,213 | 4,841 | 21,185 | 114 ms |
| Laravel laravel | 712 | 706 | 1,297 | 404 ms |
| Symfony symfony | 901 | 957 | 2,846 | 352 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.
WooCommerce
Page mix
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Home page | 1.96 | 823 ms | 979 ms | 1 s | 0% |
| Shop page | 1.96 | 1.11 s | 1.3 s | 1.34 s | 0% |
| Category page | 1.96 | 701 ms | 1.11 s | 1.21 s | 0% |
| Product page | 1.96 | 738 ms | 910 ms | 944 ms | 0% |
| Product search | 1.96 | 651 ms | 801 ms | 854 ms | 0% |
| 32 virtual users | |||||
| Home page | 1.93 | 3.06 s | 3.48 s | 3.65 s | 0% |
| Shop page | 1.93 | 4.06 s | 4.75 s | 4.88 s | 0% |
| Category page | 1.93 | 3.53 s | 4.22 s | 4.41 s | 0% |
| Product page | 1.93 | 2.97 s | 3.19 s | 3.25 s | 0% |
| Product search | 1.93 | 2.78 s | 3.11 s | 3.2 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 3.91 | 846 ms | 977 ms | 1.14 s | 0% |
| Cart | 3.91 | 664 ms | 768 ms | 962 ms | 0% |
| Checkout | 3.91 | 506 ms | 605 ms | 731 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 3.97 | 2.81 s | 3.42 s | 3.53 s | 0% |
| Cart | 3.97 | 2.89 s | 3.28 s | 3.32 s | 0% |
| Checkout | 3.97 | 2.24 s | 2.61 s | 2.69 s | 0% |
k6 with a fixed number of virtual users, 62 to 66 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 | 1.77 | 244 ms | 383 ms | 605 ms | 0% |
| Topic JSON | 0.902 | 117 ms | 152 ms | 214 ms | 0% |
| Home page | 0.902 | 218 ms | 350 ms | 455 ms | 0% |
| Categories page | 0.443 | 249 ms | 308 ms | 409 ms | 0% |
| User activity page | 0.443 | 152 ms | 312 ms | 394 ms | 0% |
| 4 virtual users | |||||
| Topic page | 3.03 | 577 ms | 884 ms | 1.53 s | 0% |
| Topic JSON | 1.52 | 295 ms | 419 ms | 451 ms | 0% |
| Home page | 1.52 | 515 ms | 716 ms | 1.16 s | 0% |
| Categories page | 0.774 | 592 ms | 799 ms | 811 ms | 0% |
| User activity page | 0.741 | 355 ms | 532 ms | 873 ms | 0% |
| 16 virtual users | |||||
| Topic page | 2.88 | 1.79 s | 2.3 s | 2.5 s | 0% |
| Topic JSON | 1.47 | 1.49 s | 1.8 s | 2.05 s | 0% |
| Home page | 1.47 | 1.72 s | 2.25 s | 2.36 s | 0% |
| Categories page | 0.762 | 1.79 s | 2.31 s | 2.74 s | 0% |
| User activity page | 0.713 | 1.56 s | 1.98 s | 2.2 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 55.8 | 80.2 ms | 189 ms | 267 ms | 0% |
| Topic JSON | 28 | 79.7 ms | 199 ms | 273 ms | 0% |
| Home page | 28 | 79.3 ms | 197 ms | 280 ms | 0% |
| Categories page | 14 | 79.4 ms | 199 ms | 278 ms | 0% |
| User activity page | 14 | 257 ms | 392 ms | 624 ms | 0% |
k6 with a fixed number of virtual users, 60 to 62 s per level, after a 22 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 488 MB of it. The container peaked at 1,469 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 7.03 | 40.4 ms | 50.4 ms | 88.7 ms | 0% |
| Post page | 17.6 | 22 ms | 28.1 ms | 38.8 ms | 0% |
| Tag page | 3.51 | 25.9 ms | 32.1 ms | 37.8 ms | 0% |
| Author page | 3.51 | 26.9 ms | 33.9 ms | 59.3 ms | 0% |
| RSS feed | 3.51 | 29 ms | 36.5 ms | 43.7 ms | 0% |
| 4 virtual users | |||||
| Home page | 9.3 | 114 ms | 163 ms | 207 ms | 0% |
| Post page | 23.3 | 77.6 ms | 111 ms | 151 ms | 0% |
| Tag page | 4.68 | 67.3 ms | 102 ms | 131 ms | 0% |
| Author page | 4.64 | 73.5 ms | 110 ms | 161 ms | 0% |
| RSS feed | 4.64 | 73.9 ms | 112 ms | 158 ms | 0% |
| 16 virtual users | |||||
| Home page | 9.51 | 417 ms | 548 ms | 605 ms | 0% |
| Post page | 23.7 | 345 ms | 464 ms | 528 ms | 0% |
| Tag page | 4.75 | 228 ms | 322 ms | 365 ms | 0% |
| Author page | 4.75 | 226 ms | 321 ms | 358 ms | 0% |
| RSS feed | 4.76 | 239 ms | 335 ms | 388 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 3.87 | 35.3 ms | 48.8 ms | 74.1 ms | 0% |
| Post editor | 11.6 | 15.8 ms | 20.7 ms | 26.9 ms | 0% |
| Saving a draft | 11.6 | 39.3 ms | 52 ms | 70.6 ms | 0% |
| Member list | 3.87 | 39.1 ms | 53.6 ms | 62.2 ms | 0% |
| 4 virtual users | |||||
| Post list | 4.81 | 45.5 ms | 63.2 ms | 104 ms | 0% |
| Post editor | 14.5 | 27.6 ms | 39.5 ms | 60.8 ms | 0% |
| Saving a draft | 14.5 | 200 ms | 278 ms | 336 ms | 0% |
| Member list | 4.85 | 53.6 ms | 71.9 ms | 129 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 356 MB and MySQL at 597 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.45 | 91.7 ms | 110 ms | 118 ms | 0% |
| Blog index | 1.45 | 309 ms | 359 ms | 375 ms | 0% |
| Blog post | 4.31 | 29.5 ms | 42.7 ms | 50.7 ms | 0% |
| Bread page | 4.33 | 32.4 ms | 40.3 ms | 43.1 ms | 0% |
| Location page | 1.45 | 30.5 ms | 39.5 ms | 43.8 ms | 0% |
| Site search | 1.43 | 50.4 ms | 87.1 ms | 95.9 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.51 | 211 ms | 319 ms | 361 ms | 0% |
| Blog index | 2.56 | 752 ms | 1.04 s | 1.16 s | 0% |
| Blog post | 7.55 | 64.3 ms | 111 ms | 180 ms | 0% |
| Bread page | 7.57 | 71.2 ms | 109 ms | 128 ms | 0% |
| Location page | 2.56 | 64.9 ms | 93.7 ms | 114 ms | 0% |
| Site search | 2.52 | 106 ms | 215 ms | 239 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.31 | 787 ms | 1.06 s | 1.21 s | 0% |
| Blog index | 2.32 | 2.06 s | 2.6 s | 2.79 s | 0% |
| Blog post | 6.77 | 460 ms | 744 ms | 917 ms | 0% |
| Bread page | 6.85 | 463 ms | 767 ms | 895 ms | 0% |
| Location page | 2.29 | 472 ms | 743 ms | 891 ms | 0% |
| Site search | 2.26 | 551 ms | 845 ms | 1.05 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.643 | 97.2 ms | 121 ms | 125 ms | 0% |
| Page explorer | 1.32 | 350 ms | 459 ms | 559 ms | 0% |
| Page editor | 1.95 | 169 ms | 227 ms | 328 ms | 0% |
| Image library | 0.643 | 68.1 ms | 92.5 ms | 670 ms | 0% |
| Admin page search | 0.643 | 47.9 ms | 89 ms | 90.6 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.08 | 264 ms | 529 ms | 597 ms | 0% |
| Page explorer | 2.21 | 858 ms | 1.31 s | 1.4 s | 0% |
| Page editor | 3.31 | 381 ms | 662 ms | 844 ms | 0% |
| Image library | 1.1 | 254 ms | 470 ms | 715 ms | 0% |
| Admin page search | 1.08 | 126 ms | 313 ms | 419 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 298 MB, Postgres at 174 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
- 2A 2GB 40GB
- Product line
- Type A Availability
- 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
- $13.00
- Hourly price at test time
- $0.018
- YABS version
- v2026-09-20
- Ran at
- Oct 12, 2026, 11:05:31 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 12, 2026, 11:01:00 UTC
- First update from the server
- Oct 12, 2026, 11:04:38 UTC
- Completed
- Oct 12, 2026, 12:39:00 UTC
- Server deleted
- Oct 12, 2026, 12:39:00 UTC
- Cost of this run
- $0.029
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.