Skip to main content

Vultr High Frequency Intel 2 vCPU / 2 GB

Seattle, US

Benchmark complete
Finished Oct 14, 2026
Geekbench 7 single-core
1,529
Faster than 89% of 2 vCPU plans
Geekbench 7 multi-core
Skipped
Disk 4K IOPS
273,993
fio random read and write, 50/50
Monthly price at test time
$18.00
Same price today

Server

  • Provider
    Vultr
  • Plan
    High Frequency Intel 2 vCPU / 2 GB
  • Location
    Seattle, US
  • vCPU
    2
  • RAM
    2 GB
  • Storage
    80 GB NVMe
  • Network
    Unknown
  • OS image
    2284
  • Trigger
    Scheduled
  • Queued at
    Oct 14, 2026, 15:54:00 UTC
Visit Vultr

Referral link. If you sign up through it, I may get paid. How this works

CPU

Version Single-core Multi-core
Geekbench 7 1,529 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,452
51st of 170
Single-core only
Navigation
1,864
8th of 170
Single-core only
HTML5 Browser
1,387
52nd of 170
Single-core only
PDF Viewer
1,670
28th of 170
Single-core only
Photo Library
1,264
63rd of 170
Single-core only
Clang
1,474
26th of 170
Single-core only
Text Processing
1,498
28th of 170
Single-core only
Asset Compression
1,233
86th of 170
Single-core only
HDR
1,437
49th of 170
Single-core only
Photo Editor
1,721
34th of 170
Single-core only
Ray Tracer
1,604
27th of 170
Single-core only
Structure from Motion
1,758
25th of 170
Single-core only
Game Physics
1,432
42nd of 170
Single-core only
Video Encoder
1,536
31st of 170
Single-core only
Audio Encoder
1,618
35th of 170
Single-core only
Video Player
1,661
37th of 170
Single-core only

Rank among the 170 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 32.8 GB/s 3 2.33%
Scale higher is better 20.8 GB/s 3 4.04%
Add higher is better 22.1 GB/s 3 5.7%
Triad higher is better 22 GB/s 3 6.06%

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 402/s 3 0.423%
RSA 4096 verifies higher is better 26,459/s 3 1.5%
SHA-256 higher is better 750 MB/s 3 0.897%
AES-256-GCM higher is better 9.98 GB/s 3 0.864%
ChaCha20-Poly1305 higher is better 5.4 GB/s 3 0.756%

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.83 ms 3 0.164%
Requests per second, 90th percentile higher is better 677/s 3 0%
Request latency, 99.9th percentile lower is better 7.44 ms 3 0.448%
Requests per second, average higher is better 659/s 3 0.498%

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

Disk

Block size Read Write Total
4K 534.4 MB/s (136,816 IOPS) 535.8 MB/s (137,177 IOPS) 1.05 GB/s (273,993 IOPS)
64K 944.8 MB/s (15,116 IOPS) 949.8 MB/s (15,196 IOPS) 1.85 GB/s (30,312 IOPS)
512K 1.02 GB/s (2,080 IOPS) 1.07 GB/s (2,190 IOPS) 2.09 GB/s (4,270 IOPS)
1M 1.06 GB/s (1,088 IOPS) 1.13 GB/s (1,160 IOPS) 2.2 GB/s (2,248 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.35 Gbps 1.75 Gbps
Eranium, Amsterdam, NL (100G) IPv4 4.03 Gbps 6.55 Gbps
Leaseweb, Singapore, SG (10G) IPv4 1.18 Gbps 5.77 Gbps
Clouvider, Los Angeles, CA, US (10G) IPv4 6.19 Gbps 6.21 Gbps
Leaseweb, NYC, NY, US (10G) IPv4 8.5 Gbps 8.96 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 16,063 0.062 ms
fdatasync 14,683 0.068 ms
fsync 12,462 0.08 ms
fsync_writethrough Not supported here n/a
open_sync 14,153 0.071 ms
Two 8 kB writes
open_datasync 6,944 0.144 ms
fdatasync 13,371 0.075 ms
fsync 11,204 0.089 ms
fsync_writethrough Not supported here n/a
open_sync 6,824 0.147 ms
open_sync at different write sizes
1 * 16kB open_sync write 12,153 0.082 ms
2 * 8kB open_sync writes 6,217 0.161 ms
4 * 4kB open_sync writes 3,115 0.321 ms
8 * 2kB open_sync writes 1,520 0.658 ms
16 * 1kB open_sync writes 828 1.21 ms
fsync on a non-write descriptor
write, fsync, close 9,826 0.102 ms
write, close, fsync 10,194 0.098 ms
Non-synced 8 kB writes
write 1,058,111 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,958 0.325 ms 0.428 ms 0.5 ms 1.03 ms 0
Read/write (TPC-B like) 8 5,576 1.36 ms 2.21 ms 2.83 ms 4 ms 0
Read/write (TPC-B like) 32 5,060 5.14 ms 14.2 ms 23.6 ms 39.5 ms 0
Read only 1 30,258 0.03 ms 0.044 ms 0.054 ms 0.075 ms 0
Read only 8 51,202 0.144 ms 0.233 ms 0.289 ms 0.515 ms 0
Read only 32 50,756 0.553 ms 1.01 ms 1.37 ms 2.17 ms 0

Scale 10 (1,000,000 accounts), loaded in 1.11 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,958 0.493 ms 0.719 ms 0.904 ms 2.1 ms 0
Read/write (TPC-B like) 8 4,690 1.64 ms 2.49 ms 3.41 ms 5.17 ms 0
Read/write (TPC-B like) 32 5,318 5.69 ms 9.16 ms 11.8 ms 16.6 ms 0
Read only 1 8,827 0.062 ms 0.25 ms 0.353 ms 0.757 ms 0
Read only 8 35,377 0.193 ms 0.454 ms 0.581 ms 1.87 ms 0
Read only 32 37,170 0.75 ms 1.46 ms 1.96 ms 3.31 ms 0

Scale 100 (10,000,000 accounts), loaded in 10.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 558 11,169 1.67 ms 2.35 ms 3.62 ms 0
Read/write 8 1,043 20,853 7.43 ms 11.7 ms 15 ms 0
Read/write 32 1,111 22,218 27.2 ms 50.1 ms 65.6 ms 0
Read only 1 1,217 19,469 0.797 ms 1.01 ms 1.23 ms 0
Read only 8 2,039 32,627 3.82 ms 5.28 ms 6.1 ms 0
Read only 32 1,922 30,745 16.4 ms 20.7 ms 23.1 ms 0

10 tables of 100,000 rows, loaded in 5.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 104,674 95,158 0.479 ms 1.74 ms 2.5 ms
1:1 set:get 101,707 50,853 0.495 ms 1.86 ms 2.58 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 652 2,151 3,588 659 ms
Express express-postgresjs 7,488 11,908 33,421 65.6 ms
Fastify fastify-postgres 7,462 11,984 37,506 60.1 ms
NestJS nestjs 5,441 6,126 20,991 82.2 ms
Nuxt nuxt 6,743 11,538 31,540 70.3 ms
FastAPI fastapi 4,145 5,176 20,460 229 ms
Django django-postgresql 2,140 2,322 5,601 194 ms
Rails rails 3,368 5,008 17,653 131 ms
Laravel laravel 899 921 1,871 676 ms
Symfony symfony 1,203 1,286 3,451 257 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 2.69 589 ms 661 ms 708 ms 0%
Shop page 2.69 813 ms 915 ms 934 ms 0%
Category page 2.69 504 ms 798 ms 831 ms 0%
Product page 2.69 540 ms 636 ms 675 ms 0%
Product search 2.69 472 ms 558 ms 595 ms 0%
32 virtual users
Home page 2.55 2.26 s 3.2 s 3.53 s 0%
Shop page 2.55 2.97 s 4.17 s 4.32 s 0%
Category page 2.55 2.64 s 3.62 s 3.96 s 0%
Product page 2.55 2.28 s 2.6 s 2.67 s 0%
Product search 2.55 2.08 s 2.27 s 2.34 s 0%

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 5.24 629 ms 735 ms 780 ms 0%
Cart 5.24 505 ms 588 ms 653 ms 0%
Checkout 5.24 390 ms 454 ms 468 ms 0%
32 virtual users
Add to cart 5.27 2.07 s 2.58 s 2.72 s 0%
Cart 5.27 2.17 s 2.44 s 2.56 s 0%
Checkout 5.27 1.69 s 1.96 s 2.05 s 0%

k6 with a fixed number of virtual users, 61 to 65 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 2.58 171 ms 209 ms 285 ms 0%
Topic JSON 1.29 90.2 ms 112 ms 171 ms 0%
Home page 1.31 155 ms 251 ms 320 ms 0%
Categories page 0.646 179 ms 210 ms 231 ms 0%
User activity page 0.646 106 ms 163 ms 251 ms 0%
4 virtual users
Topic page 4.25 409 ms 627 ms 914 ms 0%
Topic JSON 2.13 225 ms 310 ms 409 ms 0%
Home page 2.1 363 ms 554 ms 793 ms 0%
Categories page 1.07 432 ms 803 ms 1.19 s 0%
User activity page 1.04 246 ms 482 ms 603 ms 0%
16 virtual users
Topic page 4.06 1.51 s 2.17 s 2.77 s 0%
Topic JSON 2.05 1.25 s 1.86 s 2.32 s 0%
Home page 2.1 1.4 s 2.04 s 2.54 s 0%
Categories page 0.991 1.49 s 1.92 s 1.98 s 0%
User activity page 1.06 1.26 s 1.55 s 1.98 s 0%

Anonymous

Step Requests/s Median p95 p99 Error rate
16 virtual users
Topic page 94.3 50.5 ms 107 ms 137 ms 0%
Topic JSON 47.2 48.7 ms 106 ms 140 ms 0%
Home page 47.2 48.8 ms 106 ms 134 ms 0%
Categories page 23.6 53.3 ms 115 ms 162 ms 0%
User activity page 23.6 149 ms 219 ms 266 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 had swap the way its installer sets a box up and used up to 539 MB of it. The container peaked at 1,532 MB.

Ghost

Readers

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 9.73 28.8 ms 35 ms 42.8 ms 0%
Post page 24.3 15.3 ms 19.5 ms 27.7 ms 0%
Tag page 4.86 20 ms 25.9 ms 38.8 ms 0%
Author page 4.85 19.7 ms 23.4 ms 29.4 ms 0%
RSS feed 4.85 24.5 ms 31.1 ms 35 ms 0%
4 virtual users
Home page 11.3 91.3 ms 125 ms 147 ms 0%
Post page 28.1 66.6 ms 93.9 ms 121 ms 0%
Tag page 5.64 58.6 ms 85.4 ms 114 ms 0%
Author page 5.61 57 ms 81.5 ms 98.5 ms 0%
RSS feed 5.59 61.5 ms 88.4 ms 115 ms 0%
16 virtual users
Home page 10.9 363 ms 473 ms 546 ms 0%
Post page 27.3 302 ms 397 ms 487 ms 0%
Tag page 5.47 197 ms 283 ms 328 ms 0%
Author page 5.49 194 ms 276 ms 300 ms 0%
RSS feed 5.44 207 ms 288 ms 345 ms 0%

Staff in Ghost Admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Post list 5.5 27.2 ms 41.2 ms 54.5 ms 0%
Post editor 16.6 10.4 ms 14.8 ms 21.7 ms 0%
Saving a draft 16.5 25.4 ms 34.3 ms 41.7 ms 0%
Member list 5.52 32.9 ms 42.6 ms 51.8 ms 0%
4 virtual users
Post list 6.55 39.4 ms 50.8 ms 69.3 ms 0%
Post editor 19.7 20.2 ms 27.4 ms 38.3 ms 0%
Saving a draft 19.7 149 ms 199 ms 228 ms 0%
Member list 6.57 43.2 ms 55 ms 72.1 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 360 MB and MySQL at 581 MB.

Wagtail

Visitors

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 1.98 66.6 ms 79.8 ms 87.5 ms 0%
Blog index 1.98 226 ms 264 ms 293 ms 0%
Blog post 5.9 21 ms 33.2 ms 36.8 ms 0%
Bread page 5.91 23.1 ms 27.1 ms 31.3 ms 0%
Location page 1.98 22.1 ms 26.1 ms 28.7 ms 0%
Site search 1.96 35.7 ms 60.7 ms 70.1 ms 0%
4 virtual users
Home page 3.34 170 ms 247 ms 303 ms 0%
Blog index 3.38 564 ms 860 ms 1.24 s 0%
Blog post 10 47.6 ms 79.3 ms 117 ms 0%
Bread page 10 53.5 ms 78.5 ms 106 ms 0%
Location page 3.38 47.9 ms 73.9 ms 91.6 ms 0%
Site search 3.33 72.1 ms 148 ms 180 ms 0%
16 virtual users
Home page 3.6 529 ms 727 ms 831 ms 0%
Blog index 3.61 1.26 s 1.58 s 1.72 s 0%
Blog post 10.7 297 ms 468 ms 561 ms 0%
Bread page 10.8 298 ms 487 ms 591 ms 0%
Location page 3.61 289 ms 465 ms 606 ms 0%
Site search 3.56 350 ms 565 ms 666 ms 0%

Editors in the Wagtail admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Admin dashboard 0.776 70.9 ms 89.1 ms 110 ms 0%
Page explorer 1.58 304 ms 401 ms 432 ms 0%
Page editor 2.38 139 ms 168 ms 218 ms 0%
Image library 0.792 53 ms 67.1 ms 434 ms 0%
Admin page search 0.776 28.3 ms 61.6 ms 64.5 ms 0%
4 virtual users
Admin dashboard 1.31 218 ms 396 ms 472 ms 0%
Page explorer 2.68 631 ms 1.08 s 1.25 s 0%
Page editor 4.01 341 ms 593 ms 691 ms 0%
Image library 1.33 221 ms 375 ms 464 ms 0%
Admin page search 1.33 91.6 ms 193 ms 295 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 302 MB, Postgres at 175 MB, and Redis at 26 MB.

Advertised vs. measured

Advertised Measured
vCPU 2 2
CPU Shared vCPU 0.1% of busy CPU time stolen
RAM 2 GB 1.9 GiB
Storage 80 GB NVMe 75 GiB
Architecture x86_64 x86_64
Virtualization KVM MICROSOFT

Guests usually report slightly less RAM and disk than advertised because of kernel reservations and filesystem overhead.

Detected hardware

CPU model
Intel Core Processor (Skylake, IBRS, no TSX)
CPU cores
2
CPU frequency
3696 MHz
AES-NI
Yes
VM-x/AMD-V
No
RAM reported
1.9 GiB
Swap reported
7.7 GiB
Disk reported
75 GiB
Virtualization reported
MICROSOFT
CPU steal
0.1% of busy CPU time stolen
Distro
Ubuntu 24.04.5 LTS
Kernel
6.8.0-146-generic
Architecture
x86_64
IPv4 reachable
Yes
IPv6 reachable
Yes

Advertised at test time

Plan
High Frequency Intel 2 vCPU / 2 GB
Product line
Cloud Compute High Frequency
Location
Seattle, US
vCPU
2 shared vCPU
Architecture
x86_64
RAM
2 GB
Storage
80 GB NVMe
Virtualization
KVM
Network
Unknown
Transfer
3.07 TB
Port 25
On request
Monthly price at test time
$18.00
Hourly price at test time
$0.025
YABS version
v2026-09-20
Ran at
Oct 14, 2026, 15:55:46 UTC
Parser version
5

Run timeline

Queued
Oct 14, 2026, 15:54:00 UTC
First update from the server
Oct 14, 2026, 15:54:45 UTC
Completed
Oct 14, 2026, 17:48:30 UTC
Server deleted
Oct 14, 2026, 17:48:30 UTC
Cost of this run
$0.048
Watch party 0 watching

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

Watch party

Loading the party