Skip to main content

Vultr CPU Optimized AMD 1 vCPU / 2 GB

New Jersey, US

Benchmark complete
Finished Oct 11, 2026
Geekbench 7 single-core
1,714
Geekbench 7 multi-core
Skipped
Disk 4K IOPS
117,499
fio random read and write, 50/50
Monthly price at test time
$28.00
Same price today

Server

  • Provider
    Vultr
  • Plan
    CPU Optimized AMD 1 vCPU / 2 GB
  • Location
    New Jersey, US
  • vCPU
    1
  • RAM
    2 GB
  • Storage
    25 GB NVMe
  • Network
    Unknown
  • OS image
    2284
  • Trigger
    Scheduled
  • Queued at
    Oct 11, 2026, 00:27: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,714 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,753
17th of 70
Single-core only
Navigation
1,714
6th of 70
Single-core only
HTML5 Browser
1,704
14th of 70
Single-core only
PDF Viewer
1,735
16th of 70
Single-core only
Photo Library
1,584
17th of 70
Single-core only
Clang
1,592
13th of 70
Single-core only
Text Processing
1,593
15th of 70
Single-core only
Asset Compression
1,748
15th of 70
Single-core only
HDR
1,826
13th of 70
Single-core only
Photo Editor
1,864
16th of 70
Single-core only
Ray Tracer
1,675
12th of 70
Single-core only
Structure from Motion
1,762
16th of 70
Single-core only
Game Physics
1,717
12th of 70
Single-core only
Video Encoder
1,718
14th of 70
Single-core only
Audio Encoder
1,682
18th of 70
Single-core only
Video Player
1,783
17th of 70
Single-core only

Rank among the 70 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 31.3 GB/s 3 1.4%
Scale higher is better 38.9 GB/s 3 2.76%
Add higher is better 34.8 GB/s 3 0.677%
Triad higher is better 35 GB/s 3 0.71%

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 173/s 3 2.69%
RSA 4096 verifies higher is better 11,442/s 3 0.494%
SHA-256 higher is better 998 MB/s 3 1.55%
AES-256-GCM higher is better 4.46 GB/s 3 0.183%
ChaCha20-Poly1305 higher is better 2.37 GB/s 3 0.305%

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 ms 3 0.115%
Requests per second, 90th percentile higher is better 247/s 3 0.233%
Request latency, 99.9th percentile lower is better 7.35 ms 3 0.576%
Requests per second, average higher is better 245/s 3 0.219%

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

Disk

Block size Read Write Total
4K 229.2 MB/s (58,672 IOPS) 229.8 MB/s (58,827 IOPS) 459 MB/s (117,499 IOPS)
64K 1.94 GB/s (31,822 IOPS) 1.95 GB/s (31,990 IOPS) 3.89 GB/s (63,812 IOPS)
512K 1.77 GB/s (3,623 IOPS) 1.86 GB/s (3,816 IOPS) 3.63 GB/s (7,439 IOPS)
1M 1.93 GB/s (1,978 IOPS) 2.06 GB/s (2,109 IOPS) 3.99 GB/s (4,087 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 2.58 Gbps 2.34 Gbps
Eranium, Amsterdam, NL (100G) IPv4 9.11 Gbps 5.91 Gbps
Leaseweb, Singapore, SG (10G) IPv4 2.51 Gbps 2.46 Gbps
Clouvider, Los Angeles, CA, US (10G) IPv4 busy 3.23 Gbps
Leaseweb, NYC, NY, US (10G) IPv4 7.46 Gbps 8.07 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 8,815 0.113 ms
fdatasync 8,300 0.12 ms
fsync 6,780 0.147 ms
fsync_writethrough Not supported here n/a
open_sync 7,070 0.141 ms
Two 8 kB writes
open_datasync 4,444 0.225 ms
fdatasync 8,117 0.123 ms
fsync 6,514 0.154 ms
fsync_writethrough Not supported here n/a
open_sync 3,634 0.275 ms
open_sync at different write sizes
1 * 16kB open_sync write 6,814 0.147 ms
2 * 8kB open_sync writes 3,488 0.287 ms
4 * 4kB open_sync writes 1,839 0.544 ms
8 * 2kB open_sync writes 857 1.17 ms
16 * 1kB open_sync writes 421 2.38 ms
fsync on a non-write descriptor
write, fsync, close 6,370 0.157 ms
write, close, fsync 6,409 0.156 ms
Non-synced 8 kB writes
write 652,284 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 2,826 0.337 ms 0.413 ms 0.556 ms 1.52 ms 0
Read/write (TPC-B like) 8 3,538 2.11 ms 3.36 ms 4.37 ms 6.68 ms 0
Read/write (TPC-B like) 32 3,201 8.31 ms 19.7 ms 31.4 ms 53.2 ms 0
Read only 1 38,897 0.024 ms 0.036 ms 0.049 ms 0.083 ms 0
Read only 8 37,380 0.179 ms 0.313 ms 0.385 ms 0.709 ms 0
Read only 32 36,583 0.739 ms 1.25 ms 1.45 ms 2.12 ms 0

Scale 10 (1,000,000 accounts), loaded in 1.61 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,652 0.56 ms 0.775 ms 1.59 ms 2.83 ms 0
Read/write (TPC-B like) 8 2,600 2.87 ms 4.55 ms 6.22 ms 10.2 ms 0
Read/write (TPC-B like) 32 2,896 10.3 ms 15.9 ms 20.1 ms 32.3 ms 0
Read only 1 6,984 0.172 ms 0.242 ms 0.619 ms 1.78 ms 0
Read only 8 20,808 0.272 ms 0.759 ms 1.22 ms 2.35 ms 0
Read only 32 21,983 1.2 ms 1.82 ms 2.83 ms 4.5 ms 0

Scale 100 (10,000,000 accounts), loaded in 15.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 495 9,902 1.82 ms 2.76 ms 5.09 ms 0
Read/write 8 604 12,085 12.3 ms 21.1 ms 31.9 ms 0
Read/write 32 633 12,657 45.8 ms 86 ms 115 ms 0
Read only 1 1,353 21,655 0.702 ms 0.954 ms 1.34 ms 0
Read only 8 1,278 20,453 6.1 ms 7.43 ms 9.06 ms 0
Read only 32 1,181 18,894 26.7 ms 32.5 ms 36.2 ms 0

10 tables of 100,000 rows, loaded in 12.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 38,624 35,112 1.59 ms 3.07 ms 4.22 ms
1:1 set:get 38,277 19,138 1.59 ms 3.1 ms 4.42 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 nextjs 416 1,435 2,096 1.03 s
Express express-postgresjs 4,370 6,532 23,306 774 ms
Fastify fastify-postgres 4,225 6,811 24,463 623 ms
NestJS nestjs 3,090 3,329 12,172 135 ms
Nuxt nuxt 3,931 6,623 22,258 1.25 s
FastAPI fastapi 2,298 2,851 14,549 548 ms
Django django-postgresql 1,139 1,243 2,905 264 ms
Rails rails 1,895 2,607 9,713 153 ms
Laravel laravel 507 536 953 544 ms
Symfony symfony 617 673 1,811 435 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.51 1,000 ms 1.08 s 1.09 s 0%
Shop page 1.51 1.28 s 1.42 s 1.45 s 0%
Category page 1.51 1.09 s 1.36 s 1.39 s 0%
Product page 1.51 967 ms 1.13 s 1.18 s 0%
Product search 1.51 887 ms 976 ms 985 ms 0%
32 virtual users
Home page 1.52 3.66 s 4.18 s 4.32 s 0%
Shop page 1.52 4.86 s 5.63 s 5.75 s 0%
Category page 1.52 4.49 s 5.31 s 5.48 s 0%
Product page 1.52 3.95 s 4.18 s 4.28 s 0%
Product search 1.52 3.68 s 3.95 s 4.02 s 0%

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 2.96 1.01 s 1.13 s 1.16 s 0%
Cart 2.96 903 ms 1.02 s 1.05 s 0%
Checkout 2.96 776 ms 930 ms 985 ms 0%
32 virtual users
Add to cart 3.03 3.53 s 4.39 s 4.54 s 0%
Cart 3.03 3.84 s 4.3 s 4.39 s 0%
Checkout 3.03 3 s 3.48 s 3.66 s 0%

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

Advertised vs. measured

Spec Advertised Measured
vCPU 1 1
CPU Dedicated vCPU 0% of busy CPU time stolen
RAM 2 GB 1.9 GiB
Storage 25 GB NVMe 23.4 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
AMD EPYC-Milan Processor
CPU cores
1
CPU frequency
3250 MHz
AES-NI
Yes
VM-x/AMD-V
No
RAM reported
1.9 GiB
Swap reported
2.3 GiB
Disk reported
23.4 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
CPU Optimized AMD 1 vCPU / 2 GB
Product line
Optimized Cloud CPU
Location
New Jersey, US
vCPU
1 dedicated vCPU
Architecture
x86_64
RAM
2 GB
Storage
25 GB NVMe
Virtualization
KVM
Network
Unknown
Transfer
4.1 TB
Port 25
On request
Monthly price at test time
$28.00
Hourly price at test time
$0.038
YABS version
v2026-09-20
Ran at
Oct 11, 2026, 00:29:37 UTC
Parser version
5

Run timeline

Queued
Oct 11, 2026, 00:27:00 UTC
First update from the server
Oct 11, 2026, 00:28:05 UTC
Completed
Oct 11, 2026, 01:38:43 UTC
Server deleted
Oct 11, 2026, 01:38:43 UTC
Cost of this run
$0.045
Watch party 0 watching

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

Watch party

Loading the party