Skip to main content

Vultr Regular Performance Intel 1 vCPU / 2 GB

New Jersey, US

Benchmark complete
Finished Oct 7, 2026
Geekbench 7 single-core
1,315
Geekbench 7 multi-core
Skipped
Disk 4K IOPS
131,433
fio random read and write, 50/50
Monthly price at test time
$10.00
Same price today

Server

  • Provider
    Vultr
  • Plan
    Regular Performance Intel 1 vCPU / 2 GB
  • Location
    New Jersey, US
  • vCPU
    1
  • RAM
    2 GB
  • Storage
    55 GB SSD
  • Network
    Unknown
  • OS image
    2284
  • Trigger
    Scheduled
  • Queued at
    Oct 7, 2026, 21:01: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 1,315 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
1,393
29th of 53
Single-core only
Navigation
1,696
6th of 53
Single-core only
HTML5 Browser
1,061
36th of 53
Single-core only
PDF Viewer
1,457
26th of 53
Single-core only
Photo Library
1,110
33rd of 53
Single-core only
Clang
1,147
31st of 53
Single-core only
Text Processing
988
41st of 53
Single-core only
Asset Compression
1,601
15th of 53
Single-core only
HDR
1,342
26th of 53
Single-core only
Photo Editor
1,595
22nd of 53
Single-core only
Ray Tracer
1,313
29th of 53
Single-core only
Structure from Motion
1,525
26th of 53
Single-core only
Game Physics
1,104
34th of 53
Single-core only
Video Encoder
1,213
32nd of 53
Single-core only
Audio Encoder
1,460
27th of 53
Single-core only
Video Player
1,305
33rd of 53
Single-core only

Rank among the 53 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 27.2 GB/s 3 1.74%
Scale higher is better 17.3 GB/s 3 1.61%
Add higher is better 19.2 GB/s 3 2.92%
Triad higher is better 18.7 GB/s 3 2.08%

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 193/s 3 1.74%
RSA 4096 verifies higher is better 12,432/s 3 2.53%
SHA-256 higher is better 326 MB/s 3 5.54%
AES-256-GCM higher is better 4.71 GB/s 3 0.529%
ChaCha20-Poly1305 higher is better 2.52 GB/s 3 4.12%

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.97 ms 3 1.09%
Requests per second, 90th percentile higher is better 331/s 3 1.77%
Request latency, 99.9th percentile lower is better 5.9 ms 3 8.15%
Requests per second, average higher is better 325/s 3 2.48%

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

Disk

Block size Read Write Total
4K 256.4 MB/s (65,630 IOPS) 257 MB/s (65,803 IOPS) 513.4 MB/s (131,433 IOPS)
64K 609.7 MB/s (9,755 IOPS) 612.9 MB/s (9,807 IOPS) 1.19 GB/s (19,562 IOPS)
512K 667.7 MB/s (1,335 IOPS) 703.1 MB/s (1,406 IOPS) 1.34 GB/s (2,741 IOPS)
1M 697.4 MB/s (697 IOPS) 743.8 MB/s (743 IOPS) 1.41 GB/s (1,440 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 832 Mbps 1.48 Gbps
Eranium, Amsterdam, NL (100G) IPv4 875 Mbps 1.75 Gbps
Leaseweb, Singapore, SG (10G) IPv4 705 Mbps 832 Mbps
Clouvider, Los Angeles, CA, US (10G) IPv4 878 Mbps 902 Mbps
Leaseweb, NYC, NY, US (10G) IPv4 933 Mbps 1.86 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 11,997 0.083 ms
fdatasync 11,725 0.085 ms
fsync 9,985 0.1 ms
fsync_writethrough Not supported here n/a
open_sync 11,012 0.091 ms
Two 8 kB writes
open_datasync 6,368 0.157 ms
fdatasync 10,186 0.098 ms
fsync 8,776 0.114 ms
fsync_writethrough Not supported here n/a
open_sync 5,284 0.189 ms
open_sync at different write sizes
1 * 16kB open_sync write 10,123 0.099 ms
2 * 8kB open_sync writes 5,411 0.185 ms
4 * 4kB open_sync writes 2,877 0.348 ms
8 * 2kB open_sync writes 1,369 0.731 ms
16 * 1kB open_sync writes 688 1.45 ms
fsync on a non-write descriptor
write, fsync, close 8,808 0.114 ms
write, close, fsync 8,957 0.112 ms
Non-synced 8 kB writes
write 810,060 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,693 0.358 ms 0.484 ms 0.694 ms 1.54 ms 0
Read/write (TPC-B like) 8 2,681 2.81 ms 4.52 ms 5.81 ms 7.96 ms 0
Read/write (TPC-B like) 32 2,325 11.7 ms 27.4 ms 41.6 ms 69.1 ms 0
Read only 1 26,431 0.034 ms 0.055 ms 0.066 ms 0.104 ms 0
Read only 8 25,481 0.275 ms 0.506 ms 0.636 ms 1.25 ms 0
Read only 32 22,221 1.25 ms 1.84 ms 2.27 ms 3.64 ms 0

Scale 10 (1,000,000 accounts), loaded in 1.59 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,598 0.599 ms 0.84 ms 1.45 ms 2.45 ms 0
Read/write (TPC-B like) 8 2,173 3.51 ms 5.18 ms 7.2 ms 9.77 ms 0
Read/write (TPC-B like) 32 1,988 15.4 ms 22.1 ms 26.9 ms 35 ms 0
Read only 1 6,653 0.162 ms 0.301 ms 0.496 ms 1.38 ms 0
Read only 8 14,151 0.482 ms 1.08 ms 1.61 ms 2.61 ms 0
Read only 32 12,773 2.17 ms 3.84 ms 5.32 ms 7.5 ms 0

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

MySQL

sysbench OLTP

Workload Threads Transactions/s Queries/s Median p95 p99 Errors
Read/write 1 423 8,463 2.18 ms 3.49 ms 5.99 ms 0
Read/write 8 490 9,797 15.3 ms 23.9 ms 33.1 ms 0
Read/write 32 490 9,793 61.1 ms 105 ms 137 ms 0
Read only 1 966 15,458 0.954 ms 1.44 ms 1.93 ms 0
Read only 8 895 14,316 8.58 ms 12.1 ms 14.5 ms 0
Read only 32 825 13,204 37.6 ms 50.1 ms 56.8 ms 0

10 tables of 100,000 rows, loaded in 13.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 41,926 38,114 1.48 ms 3.15 ms 5.54 ms
1:1 set:get 37,795 18,897 1.61 ms 3.52 ms 6.24 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 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

Step Requests/s Median p95 p99 Error rate
8 virtual users
Home page 0.801 1.92 s 2.27 s 2.34 s 0%
Shop page 0.801 2.55 s 2.92 s 2.96 s 0%
Category page 0.801 2.03 s 2.5 s 2.75 s 0%
Product page 0.801 1.73 s 2.07 s 2.14 s 0%
Product search 0.801 1.65 s 1.87 s 1.91 s 0%
32 virtual users
Home page 0.904 7.07 s 8.93 s 9.05 s 0%
Shop page 0.904 10.2 s 11.5 s 11.6 s 0%
Category page 0.904 8.77 s 11.1 s 11.3 s 0%
Product page 0.65 7.82 s 8.28 s 8.54 s 0%
Product search 0.452 6.73 s 7.64 s 7.73 s 0%

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 1.61 1.71 s 1.95 s 2.01 s 0%
Cart 1.61 1.59 s 1.78 s 1.92 s 0%
Checkout 1.61 1.23 s 1.48 s 1.5 s 0%
32 virtual users
Add to cart 1.81 6.14 s 8.71 s 8.93 s 0%
Cart 1.54 7.52 s 8.91 s 9.15 s 0%
Checkout 1.36 5.34 s 6.89 s 7.08 s 0%

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

Advertised vs. measured

Spec Advertised Measured
vCPU 1 1
CPU Shared vCPU 0% of busy CPU time stolen
RAM 2 GB 1.9 GiB
Storage 55 GB SSD 51.5 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
1
CPU frequency
3792 MHz
AES-NI
Yes
VM-x/AMD-V
No
RAM reported
1.9 GiB
Swap reported
5.3 GiB
Disk reported
51.5 GiB
Virtualization reported
MICROSOFT
CPU steal
0% 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 1 vCPU / 2 GB
Product line
Cloud Compute Regular
Location
New Jersey, US
vCPU
1 shared vCPU
Architecture
x86_64
RAM
2 GB
Storage
55 GB SSD
Virtualization
KVM
Network
Unknown
Transfer
2.05 TB
Port 25
On request
Monthly price at test time
$10.00
Hourly price at test time
$0.014
YABS version
v2026-09-20
Ran at
Oct 7, 2026, 21:03:38 UTC
Parser version
5

Run timeline

Queued
Oct 7, 2026, 21:01:00 UTC
Server created
Oct 7, 2026, 21:02:00 UTC
First update from the server
Oct 7, 2026, 21:02:00 UTC
Completed
Oct 7, 2026, 22:15:06 UTC
Server deleted
Oct 7, 2026, 22:15:06 UTC
Cost of this run
$0.017
Watch party 0 watching

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

Watch party

Loading the party