Skip to main content

K.N Starter 1 vCPU / 2 GB

Miami

Benchmark complete
Finished Oct 15, 2026
Geekbench 7 single-core
361
Faster than 0% of 1 vCPU plans
Geekbench 7 multi-core
Skipped
Disk 4K IOPS
17,863
fio random read and write, 50/50
Monthly price at test time
$9.99
Same price today

Server

  • Provider
    K.N
  • Plan
    Starter 1 vCPU / 2 GB
  • Location
    Miami
  • vCPU
    1
  • RAM
    2 GB
  • Storage
    20 GB SSD
  • Network
    1 Gbps
  • OS image
    ubuntu-24.04
  • Trigger
    Scheduled
  • Queued at
    Oct 15, 2026, 16:54:00 UTC
Visit K.N

CPU

Version Single-core Multi-core
Geekbench 7 361 Skipped Geekbench Browser

Multi-core was skipped because Geekbench 7 needs about 2.1 GB of free memory to run 1 thread, 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
367
191st of 191
Single-core only
Navigation
389
191st of 191
Single-core only
HTML5 Browser
400
189th of 191
Single-core only
PDF Viewer
427
191st of 191
Single-core only
Photo Library
360
186th of 191
Single-core only
Clang
329
191st of 191
Single-core only
Text Processing
325
190th of 191
Single-core only
Asset Compression
406
191st of 191
Single-core only
HDR
356
191st of 191
Single-core only
Photo Editor
449
185th of 191
Single-core only
Ray Tracer
330
191st of 191
Single-core only
Structure from Motion
384
191st of 191
Single-core only
Game Physics
271
191st of 191
Single-core only
Video Encoder
326
189th of 191
Single-core only
Audio Encoder
365
191st of 191
Single-core only
Video Player
333
189th of 191
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 7.37 GB/s 3 6.1%
Scale higher is better 8.31 GB/s 3 6.48%
Add higher is better 8.87 GB/s 3 7.68%
Triad higher is better 8.82 GB/s 3 6.66%

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 90.5/s 3 1.73%
RSA 4096 verifies higher is better 5,844/s 3 3.32%
SHA-256 higher is better 102 MB/s 3 1.29%
AES-256-GCM higher is better 1.46 GB/s 3 1.43%
ChaCha20-Poly1305 higher is better 854 MB/s 3 4.9%

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 8.74 ms 3 0.559%
Requests per second, 90th percentile higher is better 96/s 3 1.59%
Request latency, 99.9th percentile lower is better 35.1 ms 3 7.45%
Requests per second, average higher is better 94.5/s 3 0.742%

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

Disk

Block size Read Write Total
4K 34.8 MB/s (8,917 IOPS) 34.9 MB/s (8,946 IOPS) 69.8 MB/s (17,863 IOPS)
64K 297.4 MB/s (4,757 IOPS) 298.9 MB/s (4,782 IOPS) 596.3 MB/s (9,539 IOPS)
512K 487.2 MB/s (974 IOPS) 513.1 MB/s (1,026 IOPS) 1000.2 MB/s (2,000 IOPS)
1M 476.4 MB/s (476 IOPS) 508.2 MB/s (508 IOPS) 984.6 MB/s (984 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 550 Mbps 907 Mbps
Eranium, Amsterdam, NL (100G) IPv4 394 Mbps 777 Mbps
Leaseweb, Singapore, SG (10G) IPv4 321 Mbps 779 Mbps
Clouvider, Los Angeles, CA, US (10G) IPv4 620 Mbps 940 Mbps
Leaseweb, NYC, NY, US (10G) IPv4 629 Mbps 930 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,589 0.386 ms
fdatasync 1,692 0.591 ms
fsync 826 1.21 ms
fsync_writethrough Not supported here n/a
open_sync 746 1.34 ms
Two 8 kB writes
open_datasync 1,340 0.746 ms
fdatasync 1,626 0.615 ms
fsync 746 1.34 ms
fsync_writethrough Not supported here n/a
open_sync 352 2.84 ms
open_sync at different write sizes
1 * 16kB open_sync write 708 1.41 ms
2 * 8kB open_sync writes 424 2.36 ms
4 * 4kB open_sync writes 198 5.05 ms
8 * 2kB open_sync writes 101 9.89 ms
16 * 1kB open_sync writes 50.5 19.8 ms
fsync on a non-write descriptor
write, fsync, close 709 1.41 ms
write, close, fsync 734 1.36 ms
Non-synced 8 kB writes
write 410,831 0.002 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 547 1.43 ms 3.41 ms 11 ms 18.9 ms 0
Read/write (TPC-B like) 8 610 8.6 ms 41.3 ms 51.9 ms 70.2 ms 0
Read/write (TPC-B like) 32 446 61.2 ms 166 ms 250 ms 314 ms 0
Read only 1 9,740 0.066 ms 0.151 ms 0.3 ms 18.5 ms 0
Read only 8 7,547 0.603 ms 1.99 ms 14.3 ms 58.3 ms 0
Read only 32 5,481 3.03 ms 17.9 ms 29.1 ms 125 ms 0

Scale 10 (1,000,000 accounts), loaded in 5.42 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 380 2.15 ms 5.77 ms 13 ms 23.9 ms 0
Read/write (TPC-B like) 8 447 11.4 ms 50.5 ms 66.4 ms 88.1 ms 0
Read/write (TPC-B like) 32 411 73.8 ms 136 ms 274 ms 354 ms 0
Read only 1 1,366 0.572 ms 1.6 ms 3.16 ms 13 ms 0
Read only 8 2,036 2.05 ms 8.81 ms 44.6 ms 67 ms 0
Read only 32 1,902 9.1 ms 51.9 ms 64.1 ms 314 ms 0

Scale 100 (10,000,000 accounts), loaded in 65 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 68.9 1,377 10.3 ms 36.9 ms 63.3 ms 0
Read/write 8 98.5 1,970 81.5 ms 159 ms 193 ms 0
Read/write 32 120 2,398 244 ms 476 ms 646 ms 0
Read only 1 280 4,486 2.71 ms 5.67 ms 23.1 ms 0
Read only 8 247 3,946 25.3 ms 56.8 ms 162 ms 0
Read only 32 236 3,769 117 ms 244 ms 601 ms 0

10 tables of 100,000 rows, loaded in 57.6 s. 60 s per run, one connection per thread.

Redis

memtier

Mix Operations/s Hits/s Median p99 p99.9
1:10 set:get 12,599 11,453 3.86 ms 27.4 ms 37.4 ms
1:1 set:get 12,146 6,073 3.95 ms 27 ms 35.6 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 nextjs 51.2 186 226 7.55 s
Express express-postgresjs 1,320 1,607 3,576 5.52 s
Fastify fastify-postgres 1,275 1,783 4,167 5.54 s
NestJS nestjs 468 445 1,910 1.57 s
Nuxt nuxt 1,015 1,483 3,281 5.52 s
FastAPI fastapi 396 494 2,184 2.74 s
Django django-postgresql 193 219 504 1.51 s
Rails rails 341 464 1,900 870 ms
Laravel laravel 79.4 85.9 146 3.32 s
Symfony symfony 99.2 107 277 2.74 s

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

Failed: k6 summary at 32 virtual users didn't parse: k6 recorded no requests for step product

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 0.454 6.43 s 7.34 s 7.73 s 0%
Cart 0.454 6.08 s 6.66 s 7.34 s 0%
Checkout 0.454 4.47 s 5.17 s 5.18 s 0%
32 virtual users
Add to cart 0.456 17.2 s 27.7 s 27.9 s 0%
Cart 0.442 24.8 s 27.3 s 27.8 s 0%
Checkout 0.442 19.5 s 22.3 s 22.7 s 0%

k6 with a fixed number of virtual users, 70 to 72 s per level. The error rate counts responses that weren't a 200.

Discourse

Signed in

Failed: k6 summary at 4 virtual users didn't parse: k6 recorded no requests for step user_activity

Anonymous

Failed: k6 summary at 4 virtual users didn't parse: k6 recorded no requests for step user_activity

Ghost

Readers

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 1.31 208 ms 308 ms 440 ms 0%
Post page 3.26 109 ms 184 ms 268 ms 0%
Tag page 0.648 144 ms 244 ms 271 ms 0%
Author page 0.648 143 ms 232 ms 252 ms 0%
RSS feed 0.648 153 ms 257 ms 287 ms 0%
4 virtual users
Home page 1.42 707 ms 995 ms 1.39 s 0%
Post page 3.53 521 ms 799 ms 1.07 s 0%
Tag page 0.712 453 ms 652 ms 907 ms 0%
Author page 0.712 488 ms 676 ms 910 ms 0%
RSS feed 0.679 473 ms 596 ms 661 ms 0%
16 virtual users
Home page 1.4 2.93 s 3.38 s 3.47 s 0%
Post page 3.56 2.36 s 2.93 s 3.15 s 0%
Tag page 0.686 1.57 s 2.08 s 2.24 s 0%
Author page 0.702 1.49 s 2.2 s 2.33 s 0%
RSS feed 0.702 1.55 s 1.9 s 2.04 s 0%

Staff in Ghost Admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Post list 0.657 218 ms 350 ms 646 ms 0%
Post editor 2 86.4 ms 143 ms 163 ms 0%
Saving a draft 2 198 ms 290 ms 394 ms 0%
Member list 0.673 252 ms 461 ms 898 ms 0%
4 virtual users
Post list 0.72 350 ms 435 ms 469 ms 0%
Post editor 2.14 181 ms 244 ms 422 ms 0%
Saving a draft 2.18 1.34 s 1.83 s 2.13 s 0%
Member list 0.72 392 ms 587 ms 965 ms 0%

k6 with a fixed number of virtual users, 60 to 61 s per level, after a 21 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 327 MB and MySQL at 576 MB.

Wagtail

Visitors

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 0.345 370 ms 416 ms 423 ms 0%
Blog index 0.345 1.39 s 1.43 s 1.67 s 0%
Blog post 1 115 ms 174 ms 205 ms 0%
Bread page 1.02 130 ms 162 ms 178 ms 0%
Location page 0.345 121 ms 173 ms 198 ms 0%
Site search 0.329 203 ms 306 ms 372 ms 0%
4 virtual users
Home page 0.295 1.73 s 2.1 s 2.19 s 0%
Blog index 0.327 6.77 s 7.58 s 7.64 s 0%
Blog post 0.868 515 ms 860 ms 988 ms 0%
Bread page 0.917 558 ms 724 ms 790 ms 0%
Location page 0.327 520 ms 664 ms 665 ms 0%
Site search 0.278 760 ms 1.47 s 1.69 s 0%
16 virtual users
Home page 0.283 5.98 s 7.87 s 8.56 s 0%
Blog index 0.328 15.3 s 17.8 s 18.5 s 0%
Blog post 0.804 3.52 s 7.17 s 7.75 s 0%
Bread page 0.864 3.74 s 6.53 s 7.81 s 0%
Location page 0.283 3.38 s 6.16 s 6.72 s 0%
Site search 0.253 4.14 s 5.35 s 5.74 s 0%

Editors in the Wagtail admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Admin dashboard 0.127 433 ms 784 ms 900 ms 0%
Page explorer 0.269 1.63 s 2.22 s 2.4 s 0%
Page editor 0.38 756 ms 963 ms 1.14 s 0%
Image library 0.127 314 ms 2.3 s 2.97 s 0%
Admin page search 0.127 173 ms 303 ms 338 ms 0%
4 virtual users
Admin dashboard 0.107 1.81 s 2.14 s 2.15 s 0%
Page explorer 0.23 7.56 s 10.4 s 10.5 s 0%
Page editor 0.337 3.69 s 4.74 s 5.17 s 0%
Image library 0.123 1.74 s 2.18 s 2.2 s 0%
Admin page search 0.107 788 ms 1.94 s 2.04 s 0%

k6 with a fixed number of virtual users, 61 to 67 s per level, after a 23 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 281 MB, Postgres at 173 MB, and Redis at 25 MB.

Advertised vs. measured

Advertised Measured
vCPU 1 1
CPU Shared vCPU 24% of busy CPU time stolen
RAM 2 GB 1.9 GiB
Storage 20 GB SSD 19.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(R) Xeon(R) Gold 5218 CPU @ 2.30GHz
CPU cores
1
CPU frequency
2300 MHz
AES-NI
Yes
VM-x/AMD-V
Yes
RAM reported
1.9 GiB
Swap reported
0 MiB
Disk reported
19.3 GiB
Virtualization reported
KVM
CPU steal
24% 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
Starter 1 vCPU / 2 GB
Product line
Cloud Instances
Location
Miami
vCPU
1 shared vCPU
Architecture
x86_64
RAM
2 GB
Storage
20 GB SSD
Virtualization
KVM
Network
1 Gbps
Transfer
2 TB
Port 25
Unknown
Monthly price at test time
$9.99
Hourly price at test time
$0.014
YABS version
v2026-09-20
Ran at
Oct 15, 2026, 16:58:40 UTC
Parser version
5

Run timeline

Queued
Oct 15, 2026, 16:54:00 UTC
Server created
Oct 15, 2026, 16:55:30 UTC
First update from the server
Oct 15, 2026, 16:55:30 UTC
Completed
Oct 15, 2026, 19:01:10 UTC
Server deleted
Oct 15, 2026, 19:01:10 UTC
Cost of this run
$0.029
TestResultTime
Watch party 0 watching

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

Watch party

Loading the party