Skip to main content

Vultr Regular Performance Intel 2 vCPU / 2 GB

New Jersey, US

Benchmark complete
Finished Oct 10, 2026
Geekbench 7 single-core
738
Faster than 13% of 2 vCPU plans
Geekbench 7 multi-core
Skipped
Disk 4K IOPS
56,022
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
    New Jersey, US
  • vCPU
    2
  • RAM
    2 GB
  • Storage
    65 GB SSD
  • Network
    Unknown
  • OS image
    2284
  • Trigger
    Scheduled
  • Queued at
    Oct 10, 2026, 02:28:00 UTC
Visit Vultr

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

Skip the referral How this works

CPU

Version Single-core Multi-core Result link
Geekbench 7 738 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
902
55th of 61
Single-core only
Navigation
990
58th of 61
Single-core only
HTML5 Browser
545
61st of 61
Single-core only
PDF Viewer
876
57th of 61
Single-core only
Photo Library
687
55th of 61
Single-core only
Clang
736
57th of 61
Single-core only
Text Processing
372
61st of 61
Single-core only
Asset Compression
695
59th of 61
Single-core only
HDR
799
52nd of 61
Single-core only
Photo Editor
961
49th of 61
Single-core only
Ray Tracer
662
60th of 61
Single-core only
Structure from Motion
883
55th of 61
Single-core only
Game Physics
737
58th of 61
Single-core only
Video Encoder
712
56th of 61
Single-core only
Audio Encoder
870
55th of 61
Single-core only
Video Player
678
56th of 61
Single-core only

Rank among the 61 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.4 GB/s 3 1.28%
Scale higher is better 20 GB/s 3 1.72%
Add higher is better 23 GB/s 3 1.71%
Triad higher is better 22.9 GB/s 3 1.18%

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 270/s 3 1.83%
RSA 4096 verifies higher is better 17,575/s 3 1.43%
SHA-256 higher is better 399 MB/s 3 0.752%
AES-256-GCM higher is better 6.1 GB/s 3 4.7%
ChaCha20-Poly1305 higher is better 3.7 GB/s 3 0.995%

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.3 ms 3 1.71%
Requests per second, 90th percentile higher is better 417/s 3 1.96%
Request latency, 99.9th percentile lower is better 12.2 ms 3 10.4%
Requests per second, average higher is better 398/s 3 3.79%

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

Disk

Block size Read Write Total
4K 109.3 MB/s (27,974 IOPS) 109.6 MB/s (28,048 IOPS) 218.8 MB/s (56,022 IOPS)
64K 184.6 MB/s (2,953 IOPS) 185.6 MB/s (2,969 IOPS) 370.2 MB/s (5,922 IOPS)
512K 208.4 MB/s (416 IOPS) 219.5 MB/s (438 IOPS) 427.9 MB/s (854 IOPS)
1M 210.7 MB/s (210 IOPS) 224.7 MB/s (224 IOPS) 435.4 MB/s (434 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 busy 3.1 Gbps
Eranium, Amsterdam, NL (100G) IPv4 8.35 Gbps 5.3 Gbps
Leaseweb, Singapore, SG (10G) IPv4 2.93 Gbps 2.83 Gbps
Clouvider, Los Angeles, CA, US (10G) IPv4 3.34 Gbps 3.65 Gbps
Leaseweb, NYC, NY, US (10G) IPv4 8.89 Gbps 6.73 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 7,218 0.139 ms
fdatasync 6,764 0.148 ms
fsync 4,707 0.212 ms
fsync_writethrough Not supported here n/a
open_sync 4,381 0.228 ms
Two 8 kB writes
open_datasync 3,517 0.284 ms
fdatasync 5,915 0.169 ms
fsync 3,603 0.278 ms
fsync_writethrough Not supported here n/a
open_sync 2,254 0.444 ms
open_sync at different write sizes
1 * 16kB open_sync write 4,062 0.246 ms
2 * 8kB open_sync writes 2,258 0.443 ms
4 * 4kB open_sync writes 1,283 0.78 ms
8 * 2kB open_sync writes 564 1.77 ms
16 * 1kB open_sync writes 322 3.11 ms
fsync on a non-write descriptor
write, fsync, close 3,447 0.29 ms
write, close, fsync 3,568 0.28 ms
Non-synced 8 kB writes
write 564,181 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,531 0.625 ms 0.815 ms 1.08 ms 2.71 ms 0
Read/write (TPC-B like) 8 3,204 2.33 ms 4.08 ms 5.63 ms 9.21 ms 0
Read/write (TPC-B like) 32 2,957 8.6 ms 24.7 ms 42.2 ms 68.2 ms 0
Read only 1 18,423 0.05 ms 0.074 ms 0.097 ms 0.178 ms 0
Read only 8 32,478 0.223 ms 0.381 ms 0.486 ms 1.26 ms 0
Read only 32 32,548 0.85 ms 1.45 ms 1.98 ms 3.57 ms 0

Scale 10 (1,000,000 accounts), loaded in 2.97 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,076 0.87 ms 1.27 ms 2.74 ms 5.67 ms 0
Read/write (TPC-B like) 8 2,738 2.67 ms 4.96 ms 8.44 ms 16.6 ms 0
Read/write (TPC-B like) 32 2,941 10.2 ms 16.9 ms 22.5 ms 32.5 ms 0
Read only 1 3,885 0.268 ms 0.453 ms 1.49 ms 3.55 ms 0
Read only 8 18,632 0.334 ms 0.896 ms 1.94 ms 3.82 ms 0
Read only 32 19,997 1.34 ms 2.86 ms 4.25 ms 7.91 ms 0

Scale 100 (10,000,000 accounts), loaded in 29.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 239 4,775 3.68 ms 5.67 ms 18.3 ms 0
Read/write 8 537 10,733 14.5 ms 23.9 ms 33.7 ms 0
Read/write 32 558 11,162 54.8 ms 95.8 ms 119 ms 0
Read only 1 564 9,024 1.7 ms 2.31 ms 2.76 ms 0
Read only 8 1,052 16,825 7.43 ms 10.7 ms 13 ms 0
Read only 32 932 14,905 33.7 ms 45.8 ms 51.9 ms 0

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

Redis

memtier

Mix Operations/s Hits/s Median p99 p99.9
1:10 set:get 51,999 47,272 1.02 ms 3.25 ms 5.22 ms
1:1 set:get 46,717 23,358 1.14 ms 3.57 ms 5.92 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 322 1,263 1,933 1.91 s
Express express-postgresjs 5,319 7,046 19,992 176 ms
Fastify fastify-postgres 5,048 7,563 22,052 377 ms
NestJS nestjs 2,870 3,193 11,668 167 ms
Nuxt nuxt 4,231 7,026 20,081 226 ms
FastAPI fastapi 1,954 2,724 8,841 512 ms
Django django-postgresql 959 1,169 2,632 360 ms
Rails rails 1,702 2,402 8,485 222 ms
Laravel laravel 437 452 856 671 ms
Symfony symfony 483 528 1,688 582 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 1.06 1.51 s 1.71 s 1.77 s 0%
Shop page 1.06 2.02 s 2.2 s 2.33 s 0%
Category page 1.06 1.21 s 1.93 s 2.06 s 0%
Product page 1.06 1.32 s 1.51 s 1.59 s 0%
Product search 1.06 1.2 s 1.4 s 1.44 s 0%
32 virtual users
Home page 1.07 5.4 s 6.14 s 6.25 s 0%
Shop page 1.07 7.14 s 8.57 s 8.67 s 0%
Category page 1.03 6.78 s 8.3 s 8.59 s 0%
Product page 0.928 5.84 s 6.3 s 6.38 s 0%
Product search 0.9 5.34 s 5.68 s 5.73 s 0%

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 2.03 1.59 s 1.74 s 1.78 s 0%
Cart 2.03 1.27 s 1.48 s 1.52 s 0%
Checkout 2.03 1.01 s 1.13 s 1.15 s 0%
32 virtual users
Add to cart 2.08 5.1 s 6.33 s 6.59 s 0%
Cart 2.08 5.46 s 6.02 s 6.28 s 0%
Checkout 1.97 4.32 s 4.96 s 5.11 s 0%

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

Advertised vs. measured

Spec Advertised Measured
vCPU 2 2
CPU Shared vCPU 0.1% 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.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
Regular Performance Intel 2 vCPU / 2 GB
Product line
Cloud Compute Regular
Location
New Jersey, 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 10, 2026, 02:30:46 UTC
Parser version
5

Run timeline

Queued
Oct 10, 2026, 02:28:00 UTC
Server created
Oct 10, 2026, 02:29:07 UTC
First update from the server
Oct 10, 2026, 02:29:07 UTC
Completed
Oct 10, 2026, 03:46:25 UTC
Server deleted
Oct 10, 2026, 03:46:25 UTC
Cost of this run
$0.027
Watch party 0 watching

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

Watch party

Loading the party