Skip to main content

K.N Basic 2 vCPU / 2 GB

Amsterdam

Benchmark complete
Finished Oct 12, 2026
Geekbench 7 single-core
645
Faster than 11% of 2 vCPU plans
Geekbench 7 multi-core
Skipped
Disk 4K IOPS
25,511
fio random read and write, 50/50
Monthly price at test time
$14.99
Same price today

Server

  • Provider
    K.N
  • Plan
    Basic 2 vCPU / 2 GB
  • Location
    Amsterdam
  • vCPU
    2
  • RAM
    2 GB
  • Storage
    30 GB SSD
  • Network
    1 Gbps
  • OS image
    ubuntu-24.04
  • Trigger
    Scheduled
  • Queued at
    Oct 12, 2026, 12:06:00 UTC

Latest runs of this plan

Full history of this plan

CPU

Version Single-core Multi-core Result link
Geekbench 7 645 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
634
127th of 129
Single-core only
Navigation
849
122nd of 129
Single-core only
HTML5 Browser
659
119th of 129
Single-core only
PDF Viewer
733
120th of 129
Single-core only
Photo Library
599
119th of 129
Single-core only
Clang
741
114th of 129
Single-core only
Text Processing
598
120th of 129
Single-core only
Asset Compression
703
118th of 129
Single-core only
HDR
602
121st of 129
Single-core only
Photo Editor
598
118th of 129
Single-core only
Ray Tracer
579
124th of 129
Single-core only
Structure from Motion
727
121st of 129
Single-core only
Game Physics
529
126th of 129
Single-core only
Video Encoder
623
118th of 129
Single-core only
Audio Encoder
643
123rd of 129
Single-core only
Video Player
573
121st of 129
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 16.7 GB/s 3 2.33%
Scale higher is better 17.8 GB/s 3 2.76%
Add higher is better 20.2 GB/s 3 2.59%
Triad higher is better 20.1 GB/s 3 0.77%

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 222/s 3 7.59%
RSA 4096 verifies higher is better 13,771/s 3 7.12%
SHA-256 higher is better 249 MB/s 3 9.82%
AES-256-GCM higher is better 3.39 GB/s 3 1.66%
ChaCha20-Poly1305 higher is better 2 GB/s 3 1.48%

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 6.71 ms 3 2.39%
Requests per second, 90th percentile higher is better 259/s 3 3.78%
Request latency, 99.9th percentile lower is better 33.7 ms 3 1%
Requests per second, average higher is better 239/s 3 2.01%

Average of 3 runs. Spread is the standard deviation as a share of the average.

Disk

Block size Read Write Total
4K 49.8 MB/s (12,746 IOPS) 49.9 MB/s (12,765 IOPS) 99.7 MB/s (25,511 IOPS)
64K 264.5 MB/s (4,232 IOPS) 265.9 MB/s (4,254 IOPS) 530.4 MB/s (8,486 IOPS)
512K 609.9 MB/s (1,219 IOPS) 642.3 MB/s (1,284 IOPS) 1.22 GB/s (2,503 IOPS)
1M 702.6 MB/s (702 IOPS) 749.4 MB/s (749 IOPS) 1.42 GB/s (1,451 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 1 Gbps 961 Mbps
Eranium, Amsterdam, NL (100G) IPv4 1.01 Gbps 976 Mbps
Leaseweb, Singapore, SG (10G) IPv4 323 Mbps 735 Mbps
Clouvider, Los Angeles, CA, US (10G) IPv4 259 Mbps 848 Mbps
Leaseweb, NYC, NY, US (10G) IPv4 571 Mbps 904 Mbps

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 2,742 0.365 ms
fdatasync 2,638 0.379 ms
fsync 743 1.35 ms
fsync_writethrough Not supported here n/a
open_sync 705 1.42 ms
Two 8 kB writes
open_datasync 1,431 0.699 ms
fdatasync 1,907 0.524 ms
fsync 717 1.39 ms
fsync_writethrough Not supported here n/a
open_sync 391 2.56 ms
open_sync at different write sizes
1 * 16kB open_sync write 763 1.31 ms
2 * 8kB open_sync writes 384 2.6 ms
4 * 4kB open_sync writes 198 5.06 ms
8 * 2kB open_sync writes 112 8.97 ms
16 * 1kB open_sync writes 53.1 18.8 ms
fsync on a non-write descriptor
write, fsync, close 708 1.41 ms
write, close, fsync 926 1.08 ms
Non-synced 8 kB writes
write 727,300 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 502 1.89 ms 3.19 ms 4.14 ms 6.8 ms 0
Read/write (TPC-B like) 8 1,605 3.55 ms 15.8 ms 29.9 ms 38.8 ms 0
Read/write (TPC-B like) 32 1,568 13.2 ms 59.7 ms 88.1 ms 154 ms 0
Read only 1 8,155 0.114 ms 0.195 ms 0.264 ms 0.522 ms 0
Read only 8 25,340 0.198 ms 0.455 ms 0.978 ms 23.2 ms 0
Read only 32 23,388 0.491 ms 2.97 ms 21.3 ms 50.5 ms 0

Scale 10 (1,000,000 accounts), loaded in 3.3 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 422 2.2 ms 3.88 ms 6.12 ms 9.34 ms 0
Read/write (TPC-B like) 8 1,188 4.38 ms 24.7 ms 34 ms 39.4 ms 0
Read/write (TPC-B like) 32 1,352 16 ms 60.5 ms 79.7 ms 112 ms 0
Read only 1 1,631 0.578 ms 1.28 ms 2.2 ms 4.16 ms 0
Read only 8 7,513 0.497 ms 1.76 ms 11.3 ms 42.1 ms 0
Read only 32 10,654 0.895 ms 7.13 ms 44.2 ms 83.4 ms 0

Scale 100 (10,000,000 accounts), loaded in 32.2 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 115 2,302 7.84 ms 13.5 ms 28.2 ms 0
Read/write 8 271 5,419 22.7 ms 61.1 ms 80 ms 0
Read/write 32 331 6,630 92.4 ms 180 ms 219 ms 0
Read only 1 314 5,022 3.08 ms 4.57 ms 5.57 ms 0
Read only 8 803 12,848 6.67 ms 30.8 ms 75.8 ms 0
Read only 32 735 11,757 34.3 ms 84.5 ms 272 ms 0

10 tables of 100,000 rows, loaded in 23.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 36,855 33,504 1.21 ms 16.8 ms 24.4 ms
1:1 set:get 36,915 18,457 1.18 ms 17.3 ms 25.7 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 192 722 1,044 3.1 s
Express express-postgresjs 3,624 5,166 13,461 850 ms
Fastify fastify-postgres 3,633 5,170 14,898 176 ms
NestJS nestjs 1,786 1,873 6,808 284 ms
Nuxt nuxt 3,007 4,704 11,589 657 ms
FastAPI fastapi 1,477 1,949 6,877 643 ms
Django django-postgresql 709 784 1,841 682 ms
Rails rails 1,235 1,612 6,370 374 ms
Laravel laravel 304 329 575 1.02 s
Symfony symfony 397 409 1,150 834 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 0.834 1.8 s 2.4 s 2.66 s 0%
Shop page 0.834 2.59 s 3.06 s 3.29 s 0%
Category page 0.834 1.6 s 2.45 s 2.66 s 0%
Product page 0.834 1.68 s 2.03 s 2.17 s 0%
Product search 0.834 1.42 s 1.83 s 2.03 s 0%
32 virtual users
Home page 0.89 6.58 s 7.97 s 8.45 s 0%
Shop page 0.89 8.92 s 10.6 s 11.2 s 0%
Category page 0.89 7.95 s 9.67 s 10.3 s 0%
Product page 0.848 7.13 s 8.46 s 8.68 s 0%
Product search 0.473 6.03 s 7.4 s 7.64 s 0%

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 1.53 2.05 s 2.57 s 2.68 s 0%
Cart 1.53 1.61 s 2.04 s 2.28 s 0%
Checkout 1.53 1.16 s 1.55 s 1.73 s 0%
32 virtual users
Add to cart 1.78 6.66 s 8.29 s 8.81 s 0%
Cart 1.56 7.21 s 8.04 s 8.61 s 0%
Checkout 1.34 5.31 s 6.69 s 7.19 s 0%

k6 with a fixed number of virtual users, 66 to 72 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 0.722 609 ms 759 ms 840 ms 0%
Topic JSON 0.361 318 ms 662 ms 765 ms 0%
Home page 0.377 513 ms 609 ms 854 ms 0%
Categories page 0.18 644 ms 681 ms 692 ms 0%
User activity page 0.18 366 ms 527 ms 553 ms 0%
4 virtual users
Topic page 1.36 1.25 s 1.68 s 2.4 s 0%
Topic JSON 0.697 660 ms 899 ms 997 ms 0%
Home page 0.664 1.12 s 1.58 s 1.79 s 0%
Categories page 0.373 1.39 s 1.78 s 2.03 s 0%
User activity page 0.324 796 ms 1.11 s 1.51 s 0%
16 virtual users
Topic page 1.17 2.58 s 3.55 s 4.06 s 0%
Topic JSON 0.538 1.8 s 2.39 s 2.46 s 0%
Home page 0.57 2.5 s 3.23 s 3.42 s 0%
Categories page 0.269 2.74 s 3.36 s 3.89 s 0%
User activity page 0.301 1.99 s 2.8 s 3.03 s 0%

Anonymous

Step Requests/s Median p95 p99 Error rate
16 virtual users
Topic page 24.7 188 ms 413 ms 583 ms 0.468%
Topic JSON 12.4 191 ms 450 ms 684 ms 0.668%
Home page 12.3 191 ms 413 ms 578 ms 0.402%
Categories page 6.18 195 ms 503 ms 721 ms 0.267%
User activity page 6.18 549 ms 931 ms 1.48 s 0.802%

k6 with a fixed number of virtual users, 61 to 63 s per level, after a 23 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 427 MB of it. The container peaked at 1,459 MB.

Ghost

Readers

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 2.99 100 ms 131 ms 165 ms 0%
Post page 7.43 48.5 ms 65.6 ms 92.7 ms 0%
Tag page 1.5 63.9 ms 82.4 ms 96.8 ms 0%
Author page 1.48 66.4 ms 91.6 ms 102 ms 0%
RSS feed 1.48 73.8 ms 96.1 ms 144 ms 0%
4 virtual users
Home page 3.75 299 ms 419 ms 495 ms 0%
Post page 9.4 186 ms 277 ms 383 ms 0%
Tag page 1.88 181 ms 269 ms 413 ms 0%
Author page 1.88 191 ms 262 ms 275 ms 0%
RSS feed 1.88 185 ms 259 ms 293 ms 0%
16 virtual users
Home page 3.72 1.09 s 1.34 s 1.43 s 0%
Post page 9.21 917 ms 1.17 s 1.24 s 0%
Tag page 1.81 600 ms 844 ms 859 ms 0%
Author page 1.83 595 ms 816 ms 876 ms 0%
RSS feed 1.84 613 ms 812 ms 870 ms 0%

Staff in Ghost Admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Post list 1.74 87.8 ms 114 ms 197 ms 0%
Post editor 5.24 32.7 ms 48 ms 62.7 ms 0%
Saving a draft 5.24 84 ms 110 ms 117 ms 0%
Member list 1.74 106 ms 132 ms 153 ms 0%
4 virtual users
Post list 2.23 109 ms 153 ms 256 ms 0%
Post editor 6.79 54.2 ms 80.2 ms 111 ms 0%
Saving a draft 6.82 429 ms 577 ms 661 ms 0%
Member list 2.27 130 ms 174 ms 262 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. 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 343 MB and MySQL at 577 MB.

Wagtail

Visitors

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 0.579 215 ms 270 ms 280 ms 0%
Blog index 0.579 779 ms 890 ms 932 ms 0%
Blog post 1.7 76.9 ms 120 ms 136 ms 0%
Bread page 1.72 80.7 ms 116 ms 130 ms 0%
Location page 0.579 77.9 ms 114 ms 131 ms 0%
Site search 0.562 123 ms 222 ms 237 ms 0%
4 virtual users
Home page 1.12 461 ms 709 ms 751 ms 0%
Blog index 1.13 1.71 s 2.44 s 2.56 s 0%
Blog post 3.35 146 ms 237 ms 393 ms 0%
Bread page 3.37 164 ms 247 ms 291 ms 0%
Location page 1.15 171 ms 256 ms 311 ms 0%
Site search 1.1 231 ms 426 ms 528 ms 0%
16 virtual users
Home page 1.19 1.61 s 2.17 s 2.35 s 0%
Blog index 1.25 3.72 s 4.44 s 4.64 s 0%
Blog post 3.59 836 ms 1.51 s 1.71 s 0%
Bread page 3.62 890 ms 1.41 s 1.58 s 0%
Location page 1.2 883 ms 1.33 s 1.61 s 0%
Site search 1.22 1.01 s 1.46 s 1.54 s 0%

Editors in the Wagtail admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Admin dashboard 0.259 234 ms 295 ms 320 ms 0%
Page explorer 0.534 883 ms 998 ms 1.13 s 0%
Page editor 0.777 409 ms 608 ms 819 ms 0%
Image library 0.259 152 ms 685 ms 1.82 s 0%
Admin page search 0.259 97.2 ms 227 ms 240 ms 0%
4 virtual users
Admin dashboard 0.385 661 ms 1.12 s 1.2 s 0%
Page explorer 0.819 2.18 s 3.56 s 3.82 s 0%
Page editor 1.22 1 s 1.66 s 1.78 s 0%
Image library 0.418 638 ms 1.17 s 1.33 s 0%
Admin page search 0.385 259 ms 537 ms 757 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. 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 289 MB, Postgres at 175 MB, and Redis at 26 MB.

Advertised vs. measured

Spec Advertised Measured
vCPU 2 2
CPU Shared vCPU 1.9% of busy CPU time stolen
RAM 2 GB 1.9 GiB
Storage 30 GB SSD 29 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(R) Xeon(R) Silver 4216 CPU @ 2.10GHz
CPU cores
2
CPU frequency
2100 MHz
AES-NI
Yes
VM-x/AMD-V
Yes
RAM reported
1.9 GiB
Swap reported
0 MiB
Disk reported
29 GiB
Virtualization reported
KVM
CPU steal
1.9% of busy CPU time stolen
Distro
Ubuntu 24.04.4 LTS
Kernel
6.8.0-117-generic
Architecture
x86_64
IPv4 reachable
Yes
IPv6 reachable
No

Advertised at test time

Plan
Basic 2 vCPU / 2 GB
Product line
Cloud Instances
Location
Amsterdam
vCPU
2 shared vCPU
Architecture
x86_64
RAM
2 GB
Storage
30 GB SSD
Virtualization
KVM
Network
1 Gbps
Transfer
3 TB
Port 25
Unknown
Monthly price at test time
$14.99
Hourly price at test time
$0.021
YABS version
v2026-09-20
Ran at
Oct 12, 2026, 12:08:22 UTC
Parser version
5

Run timeline

Queued
Oct 12, 2026, 12:06:00 UTC
First update from the server
Oct 12, 2026, 12:06:54 UTC
Completed
Oct 12, 2026, 13:53:05 UTC
Server deleted
Oct 12, 2026, 13:53:05 UTC
Cost of this run
$0.037
Watch party 0 watching

This party closed at . It's read only now.

Watch party

Loading the party