Kamatera 2D 2GB 40GB
Server
-
ProviderKamatera
-
Plan2D 2GB 40GB
-
LocationAtlanta
-
vCPU2
-
RAM2 GB
-
Storage40 GB SSD
-
NetworkUnknown
-
OS imageubuntu_server_24.04_64-bit
-
TriggerScheduled
-
Queued atOct 15, 2026, 12:51:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,215 | 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,112
|
Single-core only |
| HTML5 Browser |
1,244
|
Single-core only |
| PDF Viewer |
1,461
|
Single-core only |
| Photo Library |
1,185
|
Single-core only |
| Clang |
1,086
|
Single-core only |
| Text Processing |
1,199
|
Single-core only |
| Asset Compression |
1,419
|
Single-core only |
| HDR |
1,183
|
Single-core only |
| Photo Editor |
1,487
|
Single-core only |
| Ray Tracer |
1,090
|
Single-core only |
| Structure from Motion |
1,376
|
Single-core only |
| Game Physics |
1,053
|
Single-core only |
| Video Encoder |
1,133
|
Single-core only |
| Audio Encoder |
1,092
|
Single-core only |
| Video Player |
1,101
|
Single-core only |
Rank among the 191 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.6 GB/s | 3 | 12% |
| Scale higher is better | 24.5 GB/s | 3 | 3.25% |
| Add higher is better | 29.8 GB/s | 3 | 4.2% |
| Triad higher is better | 28.3 GB/s | 3 | 8.86% |
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 | 944/s | 3 | 1.71% |
| RSA 4096 verifies higher is better | 27,454/s | 3 | 0.882% |
| SHA-256 higher is better | 1.52 GB/s | 3 | 5.03% |
| AES-256-GCM higher is better | 22.6 GB/s | 3 | 1.79% |
| ChaCha20-Poly1305 higher is better | 6.71 GB/s | 3 | 1.8% |
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.56 ms | 3 | 0.828% |
| Requests per second, 90th percentile higher is better | 723/s | 3 | 1.54% |
| Request latency, 99.9th percentile lower is better | 7.02 ms | 3 | 9.13% |
| Requests per second, average higher is better | 676/s | 3 | 2.22% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 165 MB/s (42,242 IOPS) | 165.4 MB/s (42,354 IOPS) | 330.5 MB/s (84,596 IOPS) |
| 64K | 1.61 GB/s (26,420 IOPS) | 1.62 GB/s (26,559 IOPS) | 3.23 GB/s (52,979 IOPS) |
| 512K | 3.14 GB/s (6,425 IOPS) | 3.3 GB/s (6,766 IOPS) | 6.44 GB/s (13,191 IOPS) |
| 1M | 3.52 GB/s (3,603 IOPS) | 3.75 GB/s (3,843 IOPS) | 7.27 GB/s (7,446 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.98 Gbps | 2.56 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.67 Gbps | 2.38 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 885 Mbps | 1.06 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.76 Gbps | 3.89 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 4.34 Gbps | 4.13 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,438 | 0.155 ms |
| fdatasync | 6,009 | 0.166 ms |
| fsync | 4,293 | 0.233 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 4,801 | 0.208 ms |
| Two 8 kB writes | ||
| open_datasync | 2,600 | 0.385 ms |
| fdatasync | 5,748 | 0.174 ms |
| fsync | 4,509 | 0.222 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 2,189 | 0.457 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 4,211 | 0.237 ms |
| 2 * 8kB open_sync writes | 2,312 | 0.432 ms |
| 4 * 4kB open_sync writes | 1,137 | 0.88 ms |
| 8 * 2kB open_sync writes | 577 | 1.73 ms |
| 16 * 1kB open_sync writes | 287 | 3.49 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 4,298 | 0.233 ms |
| write, close, fsync | 4,273 | 0.234 ms |
| Non-synced 8 kB writes | ||
| write | 1,520,506 | 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 | 1,911 | 0.457 ms | 0.951 ms | 1.86 ms | 4.57 ms | 0 |
| Read/write (TPC-B like) | 8 | 5,092 | 1.36 ms | 3.03 ms | 4.95 ms | 9.75 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,431 | 5.52 ms | 17.7 ms | 31.2 ms | 52.3 ms | 0 |
| Read only | 1 | 23,223 | 0.042 ms | 0.087 ms | 0.167 ms | 0.333 ms | 0 |
| Read only | 8 | 59,827 | 0.117 ms | 0.224 ms | 0.306 ms | 0.948 ms | 0 |
| Read only | 32 | 57,969 | 0.468 ms | 0.936 ms | 1.36 ms | 2.69 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,094 | 0.797 ms | 1.67 ms | 3.73 ms | 7.92 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,769 | 1.77 ms | 4.67 ms | 7.57 ms | 13.3 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,961 | 7.35 ms | 13.8 ms | 19.2 ms | 31.4 ms | 0 |
| Read only | 1 | 6,905 | 0.111 ms | 0.35 ms | 0.745 ms | 2.69 ms | 0 |
| Read only | 8 | 34,968 | 0.17 ms | 0.519 ms | 1.04 ms | 2.58 ms | 0 |
| Read only | 32 | 32,600 | 0.812 ms | 1.87 ms | 2.88 ms | 5.56 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 13.5 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 | 323 | 6,458 | 2.76 ms | 5.47 ms | 8.58 ms | 0 |
| Read/write | 8 | 950 | 18,992 | 7.84 ms | 13.5 ms | 19 ms | 0 |
| Read/write | 32 | 974 | 19,477 | 31.9 ms | 54.8 ms | 71.8 ms | 0 |
| Read only | 1 | 811 | 12,972 | 1.21 ms | 1.96 ms | 2.43 ms | 0 |
| Read only | 8 | 2,014 | 32,219 | 3.75 ms | 6.1 ms | 7.57 ms | 0 |
| Read only | 32 | 1,674 | 26,777 | 18.3 ms | 28.2 ms | 33.7 ms | 0 |
10 tables of 100,000 rows, loaded in 7.9 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 81,677 | 74,252 | 0.535 ms | 2.9 ms | 4.54 ms |
| 1:1 set:get | 82,929 | 41,464 | 0.511 ms | 2.9 ms | 4.54 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 | 299 | 1,248 | 1,550 | 1.4 s |
| Express express-postgresjs | 6,657 | 10,187 | 48,145 | 73.3 ms |
| Fastify fastify-postgres | 6,048 | 10,846 | 46,292 | 85.7 ms |
| NestJS nestjs | 4,934 | 4,874 | 26,272 | 118 ms |
| Nuxt nuxt | 5,404 | 10,093 | 39,604 | 362 ms |
| FastAPI fastapi | 3,349 | 4,438 | 19,410 | 329 ms |
| Django django-postgresql | 1,053 | 1,257 | 2,813 | 337 ms |
| Rails rails | 1,693 | 2,583 | 13,017 | 194 ms |
| Laravel laravel | 617 | 648 | 1,159 | 462 ms |
| Symfony symfony | 758 | 823 | 2,508 | 401 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 | 1.81 | 872 ms | 986 ms | 1.02 s | 0% |
| Shop page | 1.81 | 1.2 s | 1.37 s | 1.49 s | 0% |
| Category page | 1.81 | 728 ms | 1.22 s | 1.3 s | 0% |
| Product page | 1.81 | 792 ms | 906 ms | 982 ms | 0% |
| Product search | 1.81 | 682 ms | 767 ms | 808 ms | 0% |
| 32 virtual users | |||||
| Home page | 1.85 | 3.14 s | 3.46 s | 3.51 s | 0% |
| Shop page | 1.85 | 4.16 s | 5.06 s | 5.29 s | 0% |
| Category page | 1.85 | 3.69 s | 4.63 s | 4.86 s | 0% |
| Product page | 1.85 | 3.13 s | 3.4 s | 3.52 s | 0% |
| Product search | 1.85 | 2.96 s | 3.19 s | 3.3 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 3.51 | 937 ms | 1.1 s | 1.26 s | 0% |
| Cart | 3.51 | 729 ms | 879 ms | 954 ms | 0% |
| Checkout | 3.51 | 556 ms | 667 ms | 767 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 3.54 | 3.1 s | 3.94 s | 4.25 s | 0% |
| Cart | 3.54 | 3.23 s | 3.65 s | 3.87 s | 0% |
| Checkout | 3.54 | 2.53 s | 2.95 s | 3.04 s | 0% |
k6 with a fixed number of virtual users, 62 to 69 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.53 | 286 ms | 535 ms | 698 ms | 0% |
| Topic JSON | 0.775 | 144 ms | 190 ms | 211 ms | 0% |
| Home page | 0.775 | 247 ms | 352 ms | 479 ms | 0% |
| Categories page | 0.396 | 294 ms | 343 ms | 356 ms | 0% |
| User activity page | 0.379 | 183 ms | 298 ms | 308 ms | 0% |
| 4 virtual users | |||||
| Topic page | 2.22 | 769 ms | 1.09 s | 1.38 s | 0% |
| Topic JSON | 1.13 | 403 ms | 529 ms | 592 ms | 0% |
| Home page | 1.12 | 716 ms | 1.57 s | 1.81 s | 0% |
| Categories page | 0.592 | 857 ms | 1.11 s | 1.76 s | 0% |
| User activity page | 0.543 | 473 ms | 649 ms | 1.5 s | 0% |
| 16 virtual users | |||||
| Topic page | 2.42 | 1.87 s | 2.45 s | 2.85 s | 0% |
| Topic JSON | 1.22 | 1.55 s | 1.93 s | 2.03 s | 0% |
| Home page | 1.24 | 1.85 s | 2.41 s | 2.76 s | 0% |
| Categories page | 0.644 | 1.91 s | 2.33 s | 2.62 s | 0% |
| User activity page | 0.596 | 1.62 s | 2 s | 2.07 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 52.2 | 88.1 ms | 209 ms | 288 ms | 0% |
| Topic JSON | 26.1 | 85.4 ms | 207 ms | 304 ms | 0% |
| Home page | 26.1 | 91.7 ms | 207 ms | 282 ms | 0% |
| Categories page | 13.1 | 88.5 ms | 211 ms | 285 ms | 0% |
| User activity page | 13.1 | 269 ms | 454 ms | 619 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 494 MB of it. The container peaked at 1,517 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 6.14 | 43.3 ms | 55.7 ms | 72.6 ms | 0% |
| Post page | 15.3 | 26.3 ms | 33.1 ms | 44.8 ms | 0% |
| Tag page | 3.08 | 30.5 ms | 40.6 ms | 48.8 ms | 0% |
| Author page | 3.06 | 29.2 ms | 40.5 ms | 43.8 ms | 0% |
| RSS feed | 3.06 | 34.2 ms | 46.2 ms | 64.8 ms | 0% |
| 4 virtual users | |||||
| Home page | 7.92 | 128 ms | 172 ms | 205 ms | 0% |
| Post page | 19.7 | 92.9 ms | 141 ms | 180 ms | 0% |
| Tag page | 3.96 | 80.6 ms | 114 ms | 136 ms | 0% |
| Author page | 3.94 | 84.7 ms | 118 ms | 146 ms | 0% |
| RSS feed | 3.93 | 88.6 ms | 125 ms | 179 ms | 0% |
| 16 virtual users | |||||
| Home page | 8.34 | 478 ms | 588 ms | 630 ms | 0% |
| Post page | 20.9 | 402 ms | 516 ms | 551 ms | 0% |
| Tag page | 4.15 | 261 ms | 349 ms | 401 ms | 0% |
| Author page | 4.18 | 245 ms | 353 ms | 390 ms | 0% |
| RSS feed | 4.18 | 267 ms | 365 ms | 404 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 3.27 | 41.3 ms | 57.9 ms | 87.4 ms | 0% |
| Post editor | 9.84 | 18.6 ms | 25.7 ms | 42.9 ms | 0% |
| Saving a draft | 9.84 | 47.2 ms | 62.4 ms | 84.3 ms | 0% |
| Member list | 3.28 | 45.5 ms | 57.8 ms | 71.5 ms | 0% |
| 4 virtual users | |||||
| Post list | 4.28 | 57.3 ms | 77.8 ms | 133 ms | 0% |
| Post editor | 12.9 | 31.3 ms | 46.3 ms | 99.4 ms | 0% |
| Saving a draft | 12.9 | 224 ms | 307 ms | 366 ms | 0% |
| Member list | 4.3 | 54.2 ms | 79.8 ms | 107 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 351 MB and MySQL at 585 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.22 | 108 ms | 127 ms | 136 ms | 0% |
| Blog index | 1.22 | 370 ms | 417 ms | 454 ms | 0% |
| Blog post | 3.64 | 34.4 ms | 54.8 ms | 61.3 ms | 0% |
| Bread page | 3.66 | 36.8 ms | 46.4 ms | 49.7 ms | 0% |
| Location page | 1.22 | 34.6 ms | 42.2 ms | 46.8 ms | 0% |
| Site search | 1.21 | 63 ms | 103 ms | 106 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.95 | 280 ms | 394 ms | 478 ms | 0% |
| Blog index | 2 | 968 ms | 1.31 s | 1.47 s | 0% |
| Blog post | 5.91 | 80.1 ms | 129 ms | 190 ms | 0% |
| Bread page | 5.94 | 86.7 ms | 130 ms | 162 ms | 0% |
| Location page | 2 | 85.8 ms | 121 ms | 147 ms | 0% |
| Site search | 1.97 | 126 ms | 275 ms | 321 ms | 0% |
| 16 virtual users | |||||
| Home page | 1.89 | 990 ms | 1.26 s | 1.33 s | 0% |
| Blog index | 1.97 | 2.52 s | 3.03 s | 3.25 s | 0% |
| Blog post | 5.71 | 550 ms | 853 ms | 940 ms | 0% |
| Bread page | 5.72 | 565 ms | 886 ms | 1.03 s | 0% |
| Location page | 1.93 | 561 ms | 819 ms | 898 ms | 0% |
| Site search | 1.89 | 649 ms | 1.06 s | 1.21 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.546 | 112 ms | 139 ms | 146 ms | 0% |
| Page explorer | 1.12 | 408 ms | 481 ms | 638 ms | 0% |
| Page editor | 1.69 | 194 ms | 327 ms | 471 ms | 0% |
| Image library | 0.562 | 76.2 ms | 112 ms | 734 ms | 0% |
| Admin page search | 0.546 | 52.7 ms | 99.5 ms | 113 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.905 | 313 ms | 638 ms | 754 ms | 0% |
| Page explorer | 1.84 | 1.04 s | 1.59 s | 1.68 s | 0% |
| Page editor | 2.76 | 491 ms | 886 ms | 1.09 s | 0% |
| Image library | 0.921 | 268 ms | 582 ms | 680 ms | 0% |
| Admin page search | 0.905 | 117 ms | 306 ms | 592 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 177 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Dedicated 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
- 2D 2GB 40GB
- Product line
- Type D Dedicated
- Location
- Atlanta
- vCPU
- 2 dedicated 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
- $53.00
- Hourly price at test time
- $0.073
- YABS version
- v2026-09-20
- Ran at
- Oct 15, 2026, 12:55:07 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 15, 2026, 12:51:00 UTC
- Server created
- Oct 15, 2026, 12:53:33 UTC
- First update from the server
- Oct 15, 2026, 12:53:33 UTC
- Completed
- Oct 15, 2026, 14:27:00 UTC
- Server deleted
- Oct 15, 2026, 14:27:00 UTC
- Cost of this run
- $0.12
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.