Skip to main content

Amazon Lightsail Micro, 2 TB transfer

Virginia

Benchmark complete
Finished Oct 8, 2026
Geekbench 7 single-core
Skipped
Geekbench 7 multi-core
Skipped
Disk 4K IOPS
3,089
fio random read and write, 50/50
Median here: 3,094 over 2 runs in 90 days
Monthly price at test time
$7.00
Same price today

Server

  • Provider
    Amazon Lightsail
  • Plan
    Micro, 2 TB transfer
  • Location
    Virginia
  • vCPU
    2
  • RAM
    1 GB
  • Storage
    40 GB SSD
  • Network
    Unknown
  • OS image
    ubuntu_24_04
  • Trigger
    Scheduled
  • Queued at
    Oct 7, 2026, 23:04:00 UTC
Visit Amazon Lightsail

Latest runs of this plan

Full history of this plan

CPU

Geekbench was skipped because this plan has less than 2 GB of RAM, which isn't enough for Geekbench 7 to run without swap.

Memory, TLS and scheduler

Memory bandwidth (STREAM)

Test Result Runs Spread
Copy higher is better 11.3 GB/s 3 5.76%
Scale higher is better 12.7 GB/s 3 0.933%
Add higher is better 13 GB/s 3 0.675%
Triad higher is better 13.1 GB/s 3 0.551%

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 233/s 3 0.745%
RSA 4096 verifies higher is better 14,970/s 3 4.35%
SHA-256 higher is better 258 MB/s 3 0.25%
AES-256-GCM higher is better 3.42 GB/s 3 0.0343%
ChaCha20-Poly1305 higher is better 2.21 GB/s 3 0.0608%

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 7.73 ms 3 0.12%
Requests per second, 90th percentile higher is better 256/s 3 0.226%
Request latency, 99.9th percentile lower is better 36.3 ms 3 61.7%
Requests per second, average higher is better 249/s 3 2.23%

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

Disk

Block size Read Write Total
4K 6 MB/s (1,545 IOPS) 6 MB/s (1,544 IOPS) 12.1 MB/s (3,089 IOPS)
64K 64.4 MB/s (1,030 IOPS) 64.8 MB/s (1,036 IOPS) 129.2 MB/s (2,066 IOPS)
512K 62.1 MB/s (124 IOPS) 64.9 MB/s (129 IOPS) 127 MB/s (253 IOPS)
1M 61.2 MB/s (61 IOPS) 65.7 MB/s (65 IOPS) 126.8 MB/s (126 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.33 Gbps 705 Mbps
Eranium, Amsterdam, NL (100G) IPv4 1.62 Gbps 2.6 Gbps
Leaseweb, Singapore, SG (10G) IPv4 816 Mbps 1.11 Gbps
Clouvider, Los Angeles, CA, US (10G) IPv4 2.23 Gbps 954 Mbps
Leaseweb, NYC, NY, US (10G) IPv4 4.5 Gbps 3.34 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 1,277 0.783 ms
fdatasync 1,050 0.953 ms
fsync 347 2.88 ms
fsync_writethrough Not supported here n/a
open_sync 349 2.86 ms
Two 8 kB writes
open_datasync 521 1.92 ms
fdatasync 891 1.12 ms
fsync 336 2.98 ms
fsync_writethrough Not supported here n/a
open_sync 174 5.76 ms
open_sync at different write sizes
1 * 16kB open_sync write 340 2.94 ms
2 * 8kB open_sync writes 175 5.72 ms
4 * 4kB open_sync writes 88.9 11.3 ms
8 * 2kB open_sync writes 44.3 22.5 ms
16 * 1kB open_sync writes 22.1 45.3 ms
fsync on a non-write descriptor
write, fsync, close 345 2.9 ms
write, close, fsync 346 2.89 ms
Non-synced 8 kB writes
write 1,018,998 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 644 1.44 ms 1.91 ms 2.6 ms 33.1 ms 0
Read/write (TPC-B like) 8 2,330 2.99 ms 6.39 ms 10.2 ms 27.5 ms 0
Read/write (TPC-B like) 32 2,876 8.03 ms 29.6 ms 52.4 ms 94.8 ms 0
Read only 1 16,763 0.054 ms 0.073 ms 0.115 ms 0.361 ms 0
Read only 8 36,558 0.189 ms 0.362 ms 0.462 ms 0.667 ms 0
Read only 32 34,774 0.629 ms 1.43 ms 2.34 ms 3.79 ms 0

Scale 10 (1,000,000 accounts), loaded in 3.71 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 376 2.74 ms 3.23 ms 5.52 ms 19.5 ms 0
Read/write (TPC-B like) 8 1,003 5.58 ms 15.9 ms 21.3 ms 32.8 ms 0
Read/write (TPC-B like) 32 1,042 27.5 ms 50.3 ms 74.2 ms 396 ms 0
Read only 1 931 1.22 ms 1.54 ms 2.35 ms 5.39 ms 0
Read only 8 1,608 5.04 ms 10 ms 12.3 ms 23.6 ms 0
Read only 32 1,733 20 ms 30.6 ms 36 ms 377 ms 0

Scale 100 (10,000,000 accounts), loaded in 49.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 133 2,667 7.17 ms 11 ms 23.1 ms 0
Read/write 8 461 9,223 14.2 ms 45 ms 71.8 ms 0
Read/write 32 641 12,827 47.5 ms 77.2 ms 111 ms 0
Read only 1 608 9,733 1.52 ms 2.22 ms 3.13 ms 0
Read only 8 1,180 18,883 6.55 ms 9.56 ms 11.7 ms 0
Read only 32 1,111 17,773 26.2 ms 54.8 ms 61.1 ms 0

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

Redis

memtier

Mix Operations/s Hits/s Median p99 p99.9
1:10 set:get 53,422 48,565 0.887 ms 3.31 ms 8.58 ms
1:1 set:get 49,935 24,967 0.799 ms 3.62 ms 10.3 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 The results arrived but couldn't be read, so no numbers are shown.
Express The results arrived but couldn't be read, so no numbers are shown.
Fastify The results arrived but couldn't be read, so no numbers are shown.
NestJS The results arrived but couldn't be read, so no numbers are shown.
Nuxt The results arrived but couldn't be read, so no numbers are shown.
FastAPI The results arrived but couldn't be read, so no numbers are shown.
Django The results arrived but couldn't be read, so no numbers are shown.
Rails The results arrived but couldn't be read, so no numbers are shown.
Laravel The results arrived but couldn't be read, so no numbers are shown.
Symfony The results arrived but couldn't be read, so no numbers are shown.

WooCommerce

Page mix

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

Cart and checkout

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

Advertised vs. measured

Advertised Measured
vCPU 2 2
CPU Shared vCPU 14.2% of busy CPU time stolen
RAM 1 GB 910 MiB
Storage 40 GB SSD 38.7 GiB
Architecture x86_64 x86_64
Virtualization KVM AMAZON

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) Platinum 8259CL CPU @ 2.50GHz
CPU cores
2
CPU frequency
2500 MHz
AES-NI
Yes
VM-x/AMD-V
No
RAM reported
910 MiB
Swap reported
0 MiB
Disk reported
38.7 GiB
Virtualization reported
AMAZON
CPU steal
14.2% of busy CPU time stolen
Distro
Ubuntu 24.04.4 LTS
Kernel
7.0.0-1012-aws
Architecture
x86_64
IPv4 reachable
Yes
IPv6 reachable
Yes

Advertised at test time

Plan
Micro, 2 TB transfer
Product line
General Purpose
Location
Virginia
vCPU
2 shared vCPU
Architecture
x86_64
RAM
1 GB
Storage
40 GB SSD
Virtualization
KVM
Network
Unknown
Transfer
2.05 TB
Port 25
On request
Monthly price at test time
$7.00
Hourly price at test time
$0.0094
YABS version
v2026-09-20
Ran at
Oct 7, 2026, 23:04:35 UTC
Parser version
5

Run timeline

Queued
Oct 7, 2026, 23:04:00 UTC
First update from the server
Oct 7, 2026, 23:04:28 UTC
Completed
Oct 8, 2026, 00:27:08 UTC
Server deleted
Oct 8, 2026, 00:27:08 UTC
Cost of this run
$0.013
TestResultTimevs last run
Watch party 0 watching

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

Watch party

Loading the party