Skip to main content

Vultr Regular Performance Intel 2 vCPU / 2 GB

Miami, US

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

Server

  • Provider
    Vultr
  • Plan
    Regular Performance Intel 2 vCPU / 2 GB
  • Location
    Miami, US
  • vCPU
    2
  • RAM
    2 GB
  • Storage
    65 GB SSD
  • Network
    Unknown
  • OS image
    2284
  • Trigger
    Scheduled
  • Queued at
    Oct 15, 2026, 04:18:00 UTC
Visit Vultr

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

Latest runs of this plan

Full history of this plan

CPU

Version Single-core Multi-core
Geekbench 7 706 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
886
142nd of 170
Single-core only
Navigation
938
143rd of 170
Single-core only
HTML5 Browser
544
161st of 170
Single-core only
PDF Viewer
825
145th of 170
Single-core only
Photo Library
657
142nd of 170
Single-core only
Clang
682
150th of 170
Single-core only
Text Processing
357
168th of 170
Single-core only
Asset Compression
684
150th of 170
Single-core only
HDR
771
133rd of 170
Single-core only
Photo Editor
922
120th of 170
Single-core only
Ray Tracer
631
155th of 170
Single-core only
Structure from Motion
860
138th of 170
Single-core only
Game Physics
660
148th of 170
Single-core only
Video Encoder
666
146th of 170
Single-core only
Audio Encoder
835
143rd of 170
Single-core only
Video Player
659
146th 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 19.3 GB/s 3 1.08%
Scale higher is better 19.4 GB/s 3 3.17%
Add higher is better 22.9 GB/s 3 1.53%
Triad higher is better 22.4 GB/s 3 2.26%

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 262/s 3 1.44%
RSA 4096 verifies higher is better 16,939/s 3 1.59%
SHA-256 higher is better 390 MB/s 3 2.18%
AES-256-GCM higher is better 5.77 GB/s 3 4.49%
ChaCha20-Poly1305 higher is better 3.61 GB/s 3 2.53%

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 4.36 ms 3 0.971%
Requests per second, 90th percentile higher is better 424/s 3 1.79%
Request latency, 99.9th percentile lower is better 11.6 ms 3 9.53%
Requests per second, average higher is better 404/s 3 2.3%

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

Disk

Block size Read Write Total
4K 92.1 MB/s (23,574 IOPS) 92.3 MB/s (23,637 IOPS) 184.4 MB/s (47,211 IOPS)
64K 184.5 MB/s (2,952 IOPS) 185.5 MB/s (2,967 IOPS) 370 MB/s (5,919 IOPS)
512K 206.4 MB/s (412 IOPS) 217.3 MB/s (434 IOPS) 423.7 MB/s (846 IOPS)
1M 214.1 MB/s (214 IOPS) 228.4 MB/s (228 IOPS) 442.5 MB/s (442 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.67 Gbps 876 Mbps
Eranium, Amsterdam, NL (100G) IPv4 6.48 Gbps 3.78 Gbps
Leaseweb, Singapore, SG (10G) IPv4 2.3 Gbps 2.8 Gbps
Clouvider, Los Angeles, CA, US (10G) IPv4 2.96 Gbps 1.05 Gbps
Leaseweb, NYC, NY, US (10G) IPv4 8.42 Gbps 4.76 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 2,864 0.349 ms
fdatasync 2,835 0.353 ms
fsync 1,996 0.501 ms
fsync_writethrough Not supported here n/a
open_sync 2,112 0.473 ms
Two 8 kB writes
open_datasync 2,201 0.454 ms
fdatasync 2,947 0.339 ms
fsync 2,052 0.487 ms
fsync_writethrough Not supported here n/a
open_sync 1,505 0.665 ms
open_sync at different write sizes
1 * 16kB open_sync write 2,030 0.493 ms
2 * 8kB open_sync writes 1,492 0.67 ms
4 * 4kB open_sync writes 842 1.19 ms
8 * 2kB open_sync writes 502 1.99 ms
16 * 1kB open_sync writes 290 3.45 ms
fsync on a non-write descriptor
write, fsync, close 2,042 0.49 ms
write, close, fsync 2,076 0.482 ms
Non-synced 8 kB writes
write 556,229 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 1,118 0.863 ms 1.16 ms 1.48 ms 2.95 ms 0
Read/write (TPC-B like) 8 2,866 2.55 ms 4.6 ms 6.12 ms 8.66 ms 0
Read/write (TPC-B like) 32 2,566 9.82 ms 28.9 ms 50 ms 82.9 ms 0
Read only 1 17,659 0.052 ms 0.08 ms 0.11 ms 0.195 ms 0
Read only 8 29,962 0.243 ms 0.411 ms 0.525 ms 1.27 ms 0
Read only 32 27,790 0.991 ms 1.79 ms 2.42 ms 4.84 ms 0

Scale 10 (1,000,000 accounts), loaded in 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 720 1.35 ms 1.89 ms 2.91 ms 5.72 ms 0
Read/write (TPC-B like) 8 2,271 3.27 ms 5.95 ms 8.62 ms 13.2 ms 0
Read/write (TPC-B like) 32 2,424 12.5 ms 20.6 ms 26.1 ms 35.8 ms 0
Read only 1 1,890 0.472 ms 0.953 ms 1.91 ms 3.8 ms 0
Read only 8 15,669 0.385 ms 1.13 ms 2.41 ms 4.26 ms 0
Read only 32 17,790 1.52 ms 3.24 ms 4.81 ms 9.48 ms 0

Scale 100 (10,000,000 accounts), loaded in 34.8 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

Failed: sysbench prepare output didn't parse: sysbench prepare did not fill every table it created

Redis

memtier

Mix Operations/s Hits/s Median p99 p99.9
1:10 set:get 47,393 43,084 1.11 ms 3.47 ms 5.92 ms
1:1 set:get 44,456 22,228 1.18 ms 3.74 ms 6.27 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 266 1,026 1,585 2.73 s
Express express-postgresjs 4,775 6,480 18,221 205 ms
Fastify fastify-postgres 4,574 7,021 20,566 116 ms
NestJS nestjs 2,440 2,954 11,059 200 ms
Nuxt nuxt 3,609 5,786 16,425 364 ms
FastAPI fastapi 1,666 2,361 8,199 637 ms
Django django-postgresql 808 892 2,540 454 ms
Rails rails 1,452 2,112 7,576 223 ms
Laravel laravel 341 359 640 820 ms
Symfony symfony 377 437 1,477 724 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 0.834 1.86 s 2.01 s 2.08 s 0%
Shop page 0.834 2.54 s 2.77 s 2.86 s 0%
Category page 0.834 1.6 s 2.54 s 2.67 s 0%
Product page 0.834 1.67 s 1.9 s 1.97 s 0%
Product search 0.834 1.5 s 1.65 s 1.68 s 0%
32 virtual users
Home page 0.896 7.02 s 7.93 s 8.08 s 0%
Shop page 0.896 9.14 s 10.2 s 10.4 s 0%
Category page 0.896 8.12 s 9.44 s 9.64 s 0%
Product page 0.826 7.17 s 8.15 s 8.25 s 0%
Product search 0.462 6.68 s 7.15 s 7.4 s 0%

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 1.49 2 s 2.31 s 2.41 s 0%
Cart 1.49 1.63 s 1.89 s 2.01 s 0%
Checkout 1.49 1.25 s 1.46 s 1.61 s 0%
32 virtual users
Add to cart 1.79 6.54 s 8.22 s 8.65 s 0%
Cart 1.51 7.15 s 7.99 s 8.22 s 0%
Checkout 1.34 5.52 s 6.4 s 6.72 s 0%

k6 with a fixed number of virtual users, 67 to 71 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.816 531 ms 678 ms 1.02 s 0%
Topic JSON 0.424 290 ms 344 ms 351 ms 0%
Home page 0.408 457 ms 545 ms 582 ms 0%
Categories page 0.212 559 ms 648 ms 674 ms 0%
User activity page 0.196 314 ms 557 ms 771 ms 0%
4 virtual users
Topic page 1.37 1.25 s 1.61 s 2.7 s 0%
Topic JSON 0.701 687 ms 822 ms 1.33 s 0%
Home page 0.685 1.17 s 1.34 s 1.65 s 0%
Categories page 0.359 1.33 s 1.55 s 1.58 s 0%
User activity page 0.343 735 ms 876 ms 888 ms 0%
16 virtual users
Topic page 1.21 2.58 s 3.5 s 3.75 s 0%
Topic JSON 0.628 1.88 s 2.81 s 2.98 s 0%
Home page 0.613 2.39 s 2.92 s 3.31 s 0%
Categories page 0.314 2.58 s 3.57 s 3.76 s 0%
User activity page 0.298 1.94 s 2.38 s 2.84 s 0%

Anonymous

Step Requests/s Median p95 p99 Error rate
16 virtual users
Topic page 28.5 160 ms 350 ms 476 ms 0.347%
Topic JSON 14.3 160 ms 344 ms 581 ms 0.115%
Home page 14.3 163 ms 361 ms 543 ms 0.231%
Categories page 7.18 154 ms 347 ms 469 ms 0.23%
User activity page 7.13 494 ms 756 ms 1.09 s 0%

k6 with a fixed number of virtual users, 61 to 64 s per level, after a 24 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 473 MB of it. The container peaked at 1,490 MB.

Ghost

Readers

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 3.98 74.3 ms 88.4 ms 126 ms 0%
Post page 9.92 37.5 ms 46.4 ms 62.1 ms 0%
Tag page 2 48.1 ms 61 ms 72.7 ms 0%
Author page 1.98 49 ms 57.8 ms 64.6 ms 0%
RSS feed 1.98 56 ms 65.9 ms 70.4 ms 0%
4 virtual users
Home page 4.77 236 ms 291 ms 388 ms 0%
Post page 11.9 146 ms 214 ms 283 ms 0%
Tag page 2.39 137 ms 197 ms 285 ms 0%
Author page 2.38 149 ms 198 ms 216 ms 0%
RSS feed 2.38 149 ms 211 ms 277 ms 0%
16 virtual users
Home page 4.78 854 ms 1.06 s 1.12 s 0%
Post page 11.9 697 ms 879 ms 934 ms 0%
Tag page 2.36 465 ms 616 ms 723 ms 0%
Author page 2.38 468 ms 633 ms 727 ms 0%
RSS feed 2.38 464 ms 624 ms 744 ms 0%

Staff in Ghost Admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Post list 2.2 67.3 ms 87.5 ms 149 ms 0%
Post editor 6.61 26.5 ms 35.8 ms 53.5 ms 0%
Saving a draft 6.61 65.7 ms 84.2 ms 102 ms 0%
Member list 2.2 80.3 ms 103 ms 135 ms 0%
4 virtual users
Post list 2.75 95.8 ms 112 ms 168 ms 0%
Post editor 8.3 46.7 ms 62.2 ms 121 ms 0%
Saving a draft 8.32 364 ms 456 ms 568 ms 0%
Member list 2.78 109 ms 131 ms 244 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 340 MB and MySQL at 581 MB.

Wagtail

Visitors

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 0.711 189 ms 204 ms 211 ms 0%
Blog index 0.711 632 ms 712 ms 776 ms 0%
Blog post 2.1 60.1 ms 94.1 ms 96.8 ms 0%
Bread page 2.12 65.9 ms 74.8 ms 80 ms 0%
Location page 0.711 63.5 ms 75.3 ms 78.7 ms 0%
Site search 0.694 96.9 ms 176 ms 181 ms 0%
4 virtual users
Home page 1.26 473 ms 597 ms 668 ms 0%
Blog index 1.29 1.48 s 2 s 2.22 s 0%
Blog post 3.82 126 ms 256 ms 303 ms 0%
Bread page 3.84 144 ms 203 ms 218 ms 0%
Location page 1.31 131 ms 178 ms 204 ms 0%
Site search 1.27 182 ms 430 ms 468 ms 0%
16 virtual users
Home page 1.34 1.4 s 1.78 s 1.95 s 0%
Blog index 1.35 3.52 s 4.35 s 4.89 s 0%
Blog post 3.93 761 ms 1.35 s 1.66 s 0%
Bread page 4.01 772 ms 1.24 s 1.36 s 0%
Location page 1.37 748 ms 1.15 s 1.3 s 0%
Site search 1.27 971 ms 1.6 s 1.91 s 0%

Editors in the Wagtail admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Admin dashboard 0.292 201 ms 244 ms 247 ms 0%
Page explorer 0.584 781 ms 1.05 s 1.11 s 0%
Page editor 0.877 360 ms 504 ms 671 ms 0%
Image library 0.292 132 ms 375 ms 1.34 s 0%
Admin page search 0.292 77.5 ms 142 ms 164 ms 0%
4 virtual users
Admin dashboard 0.452 511 ms 1.09 s 1.25 s 0%
Page explorer 0.969 1.9 s 3.05 s 3.32 s 0%
Page editor 1.47 923 ms 1.38 s 1.72 s 0%
Image library 0.517 438 ms 816 ms 939 ms 0%
Admin page search 0.452 236 ms 626 ms 883 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 290 MB, Postgres at 175 MB, and Redis at 26 MB.

Advertised vs. measured

Advertised Measured
vCPU 2 2
CPU Shared vCPU 0.2% of busy CPU time stolen
RAM 2 GB 1.9 GiB
Storage 65 GB SSD 60.9 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 Xeon Processor (Skylake, IBRS)
CPU cores
2
CPU frequency
2594 MHz
AES-NI
Yes
VM-x/AMD-V
No
RAM reported
1.9 GiB
Swap reported
6.2 GiB
Disk reported
60.9 GiB
Virtualization reported
MICROSOFT
CPU steal
0.2% 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
Regular Performance Intel 2 vCPU / 2 GB
Product line
Cloud Compute Regular
Location
Miami, US
vCPU
2 shared vCPU
Architecture
x86_64
RAM
2 GB
Storage
65 GB SSD
Virtualization
KVM
Network
Unknown
Transfer
3.07 TB
Port 25
On request
Monthly price at test time
$15.00
Hourly price at test time
$0.021
YABS version
v2026-09-20
Ran at
Oct 15, 2026, 04:20:55 UTC
Parser version
5

Run timeline

Queued
Oct 15, 2026, 04:18:00 UTC
First update from the server
Oct 15, 2026, 04:19:12 UTC
Completed
Oct 15, 2026, 05:52:32 UTC
Server deleted
Oct 15, 2026, 05:52:32 UTC
Cost of this run
$0.033
TestResultTime
Watch party 0 watching

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

Watch party

Loading the party