# Vultr CPU Optimized AMD 1 vCPU / 2 GB

[Los Angeles, US](https://rackcensus.com/locations/los-angeles-vps-benchmarks "Every provider in Los Angeles")

Benchmark complete

Finished Oct 11, 2026

Geekbench 7 single-core

1,762

Geekbench 7 multi-core

Skipped

Disk 4K IOPS

84,575

fio random read and write, 50/50

Monthly price at test time

$28.00

Same price today

## Server

[Vultr](https://rackcensus.com/vps-providers/vultr-benchmarks)[CPU Optimized AMD 1 vCPU / 2 GB](https://rackcensus.com/plans/a04uf6-vultr-cpu-optimized-amd-1-vcpu-2-gb-benchmarks?location=lax)

-

Provider

Vultr

-

Plan

CPU Optimized AMD 1 vCPU / 2 GB

-

Location

Los Angeles, US

-

vCPU

1

-

RAM

2 GB

-

Storage

25 GB NVMe

-

Network

Unknown

-

OS image

2284

-

Trigger

Scheduled

-

Queued at

Oct 11, 2026, 18:37:00 UTC

[Visit Vultr](https://rackcensus.com/go/vultr)

Referral link. If you sign up through it, I may get paid. [How this works](https://rackcensus.com/transparency#referrals-heading)

## Latest runs of this plan

- [Amsterdam, NL Oct 12, 2026](https://rackcensus.com/benchmarks/zc03al-vultr-cpu-optimized-amd-1-vcpu-2-gb-ams-benchmark)1,623
- [New Jersey, US Oct 11, 2026](https://rackcensus.com/benchmarks/87t7eu-vultr-cpu-optimized-amd-1-vcpu-2-gb-ewr-benchmark)1,714

[Full history of this plan](https://rackcensus.com/plans/a04uf6-vultr-cpu-optimized-amd-1-vcpu-2-gb-benchmarks/history)

## CPU

| Version | Single-core | Multi-core | Result link |
| --- | --- | --- | --- |
| Geekbench 7 | 1,762 | Skipped | [Geekbench Browser](https://browser.geekbench.com/v7/cpu/608422) |

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,77915th of 106 | Single-core only |
| Navigation | 1,8785th of 106 | Single-core only |
| HTML5 Browser | 1,81913th of 106 | Single-core only |
| PDF Viewer | 1,82516th of 106 | Single-core only |
| Photo Library | 1,63519th of 106 | Single-core only |
| Clang | 1,64313th of 106 | Single-core only |
| Text Processing | 1,63216th of 106 | Single-core only |
| Asset Compression | 1,79116th of 106 | Single-core only |
| HDR | 1,83316th of 106 | Single-core only |
| Photo Editor | 1,72628th of 106 | Single-core only |
| Ray Tracer | 1,7238th of 106 | Single-core only |
| Structure from Motion | 1,76320th of 106 | Single-core only |
| Game Physics | 1,73213th of 106 | Single-core only |
| Video Encoder | 1,79514th of 106 | Single-core only |
| Audio Encoder | 1,78517th of 106 | Single-core only |
| Video Player | 1,85918th of 106 | Single-core only |

Rank among the 106 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 GB/s | 3 | 0.734% |
| Scale higher is better | 38.6 GB/s | 3 | 2.64% |
| Add higher is better | 36.4 GB/s | 3 | 0.245% |
| Triad higher is better | 36.2 GB/s | 3 | 0.373% |

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 | 179/s | 3 | 0.0968% |
| RSA 4096 verifies higher is better | 11,705/s | 3 | 0.173% |
| SHA-256 higher is better | 1.02 GB/s | 3 | 0.323% |
| AES-256-GCM higher is better | 4.59 GB/s | 3 | 0.0938% |
| ChaCha20-Poly1305 higher is better | 2.39 GB/s | 3 | 0.263% |

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 | 3.92 ms | 3 | 0.353% |
| Requests per second, 90th percentile higher is better | 252/s | 3 | 0.229% |
| Request latency, 99.9th percentile lower is better | 7.34 ms | 3 | 0.126% |
| Requests per second, average higher is better | 252/s | 3 | 0.271% |

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

## Disk

| Block size | Read | Write | Total |
| --- | --- | --- | --- |
| 4K | 165 MB/s (42,232 IOPS) | 165.4 MB/s (42,343 IOPS) | 330.4 MB/s (84,575 IOPS) |
| 64K | 2.17 GB/s (35,523 IOPS) | 2.18 GB/s (35,710 IOPS) | 4.35 GB/s (71,233 IOPS) |
| 512K | 2.36 GB/s (4,836 IOPS) | 2.49 GB/s (5,093 IOPS) | 4.85 GB/s (9,929 IOPS) |
| 1M | 2.47 GB/s (2,528 IOPS) | 2.63 GB/s (2,696 IOPS) | 5.1 GB/s (5,224 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.3 Gbps | 1.67 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 5.57 Gbps | 8.59 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 4.58 Gbps | 5.88 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 8.46 Gbps | 9.07 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 6.3 Gbps | 7.59 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,020 | 0.091 ms |
| fdatasync | 10,442 | 0.096 ms |
| fsync | 9,012 | 0.111 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 9,592 | 0.104 ms |
| Two 8 kB writes |
| --- |
| open\_datasync | 5,385 | 0.186 ms |
| fdatasync | 9,794 | 0.102 ms |
| fsync | 8,786 | 0.114 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 4,734 | 0.211 ms |
| open\_sync at different write sizes |
| --- |
| 1 \* 16kB open\_sync write | 9,294 | 0.108 ms |
| 2 \* 8kB open\_sync writes | 4,836 | 0.207 ms |
| 4 \* 4kB open\_sync writes | 2,428 | 0.412 ms |
| 8 \* 2kB open\_sync writes | 1,176 | 0.85 ms |
| 16 \* 1kB open\_sync writes | 578 | 1.73 ms |
| fsync on a non-write descriptor |
| --- |
| write, fsync, close | 8,239 | 0.121 ms |
| write, close, fsync | 8,094 | 0.124 ms |
| Non-synced 8 kB writes |
| --- |
| write | 665,143 | 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 | 3,156 | 0.305 ms | 0.353 ms | 0.527 ms | 1.5 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,527 | 2.12 ms | 3.33 ms | 4.28 ms | 5.97 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,357 | 8.12 ms | 18.9 ms | 29.5 ms | 46.4 ms | 0 |
| Read only | 1 | 40,185 | 0.024 ms | 0.032 ms | 0.039 ms | 0.063 ms | 0 |
| Read only | 8 | 39,148 | 0.175 ms | 0.289 ms | 0.351 ms | 0.67 ms | 0 |
| Read only | 32 | 37,799 | 0.725 ms | 1.22 ms | 1.38 ms | 2.12 ms | 0 |

Scale 10 (1,000,000 accounts), loaded in 1.23 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,709 | 0.545 ms | 0.759 ms | 1.52 ms | 2.55 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,742 | 2.75 ms | 4.3 ms | 5.84 ms | 8.5 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,924 | 10.2 ms | 15.5 ms | 19.2 ms | 27.5 ms | 0 |
| Read only | 1 | 6,661 | 0.193 ms | 0.259 ms | 0.47 ms | 1.37 ms | 0 |
| Read only | 8 | 21,372 | 0.264 ms | 0.754 ms | 1.24 ms | 2.37 ms | 0 |
| Read only | 32 | 22,950 | 1.16 ms | 1.75 ms | 2.71 ms | 4.2 ms | 0 |

Scale 100 (10,000,000 accounts), loaded in 14 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 | 553 | 11,059 | 1.64 ms | 2.66 ms | 4.65 ms | 0 |
| Read/write | 8 | 638 | 12,762 | 11.4 ms | 20 ms | 31.9 ms | 0 |
| Read/write | 32 | 679 | 13,578 | 42.6 ms | 83 ms | 111 ms | 0 |
| Read only | 1 | 1,432 | 22,917 | 0.665 ms | 0.92 ms | 1.32 ms | 0 |
| Read only | 8 | 1,355 | 21,686 | 5.88 ms | 6.67 ms | 7.7 ms | 0 |
| Read only | 32 | 1,261 | 20,176 | 25.3 ms | 29.2 ms | 31.9 ms | 0 |

10 tables of 100,000 rows, loaded in 10.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 | 39,981 | 36,346 | 1.55 ms | 2.98 ms | 4.16 ms |
| 1:1 set:get | 39,681 | 19,840 | 1.55 ms | 3.01 ms | 4.22 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 | 427 | 1,455 | 2,136 | 939 ms |
| Express express-postgresjs | 4,425 | 6,763 | 24,320 | 614 ms |
| Fastify fastify-postgres | 4,346 | 6,965 | 25,973 | 700 ms |
| NestJS nestjs | 3,271 | 3,510 | 13,143 | 128 ms |
| Nuxt nuxt | 4,103 | 6,845 | 23,921 | 1.14 s |
| FastAPI fastapi | 2,405 | 3,016 | 15,220 | 429 ms |
| Django django-postgresql | 1,181 | 1,284 | 3,066 | 241 ms |
| Rails rails | 1,945 | 2,770 | 10,552 | 140 ms |
| Laravel laravel | 536 | 565 | 990 | 487 ms |
| Symfony symfony | 640 | 697 | 1,893 | 413 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.62 | 940 ms | 1.15 s | 1.19 s | 0% |
| Shop page | 1.62 | 1.18 s | 1.35 s | 1.38 s | 0% |
| Category page | 1.62 | 968 ms | 1.27 s | 1.32 s | 0% |
| Product page | 1.62 | 900 ms | 1.1 s | 1.12 s | 0% |
| Product search | 1.62 | 824 ms | 916 ms | 947 ms | 0% |
| 32 virtual users |
| --- |
| Home page | 1.82 | 3.53 s | 3.94 s | 4.01 s | 0% |
| Shop page | 1.82 | 4.63 s | 5.22 s | 5.35 s | 0% |
| Category page | 1.66 | 4.3 s | 5.07 s | 5.13 s | 0% |
| Product page | 1.36 | 3.56 s | 3.72 s | 3.76 s | 0% |
| Product search | 1.36 | 3.38 s | 3.6 s | 3.65 s | 0% |

#### Cart and checkout

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 8 virtual users |
| --- |
| Add to cart | 3.04 | 951 ms | 1.06 s | 1.08 s | 0% |
| Cart | 3.04 | 866 ms | 953 ms | 963 ms | 0% |
| Checkout | 3.04 | 725 ms | 840 ms | 868 ms | 0% |
| 32 virtual users |
| --- |
| Add to cart | 3.23 | 3.28 s | 4.01 s | 4.16 s | 0% |
| Cart | 3.23 | 3.64 s | 3.93 s | 4.03 s | 0% |
| Checkout | 3.23 | 2.85 s | 3.28 s | 3.4 s | 0% |

k6 with a fixed number of virtual users, 64 to 70 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.96 | 146 ms | 209 ms | 366 ms | 0% |
| Topic JSON | 1.48 | 71.3 ms | 84.2 ms | 110 ms | 0% |
| Home page | 1.48 | 131 ms | 203 ms | 349 ms | 0% |
| Categories page | 0.741 | 154 ms | 347 ms | 388 ms | 0% |
| User activity page | 0.741 | 91.5 ms | 117 ms | 191 ms | 0% |
| 4 virtual users |
| --- |
| Topic page | 2.57 | 669 ms | 785 ms | 1.65 s | 0% |
| Topic JSON | 1.3 | 353 ms | 410 ms | 479 ms | 0% |
| Home page | 1.29 | 609 ms | 1.49 s | 1.75 s | 0% |
| Categories page | 0.676 | 700 ms | 1.02 s | 1.57 s | 0% |
| User activity page | 0.659 | 404 ms | 582 ms | 1.02 s | 0% |
| 16 virtual users |
| --- |
| Topic page | 2.3 | 1.76 s | 2.15 s | 2.48 s | 0% |
| Topic JSON | 1.15 | 1.41 s | 1.89 s | 2.15 s | 0% |
| Home page | 1.12 | 1.75 s | 2.51 s | 3.16 s | 0% |
| Categories page | 0.575 | 1.85 s | 2.15 s | 2.96 s | 0% |
| User activity page | 0.575 | 1.54 s | 2 s | 2.15 s | 0% |

#### Anonymous

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 16 virtual users |
| --- |
| Topic page | 49.5 | 88.4 ms | 221 ms | 296 ms | 0% |
| Topic JSON | 24.8 | 84.3 ms | 210 ms | 302 ms | 0% |
| Home page | 24.7 | 87.1 ms | 220 ms | 295 ms | 0% |
| Categories page | 12.4 | 89.4 ms | 231 ms | 373 ms | 0% |
| User activity page | 12.4 | 279 ms | 441 ms | 804 ms | 0% |

k6 with a fixed number of virtual users, 60 to 63 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 440 MB of it. The container peaked at 1,468 MB.

### Ghost

#### Readers

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 10.6 | 24.8 ms | 34.4 ms | 70.1 ms | 0% |
| Post page | 26.4 | 13.5 ms | 20.6 ms | 41.9 ms | 0% |
| Tag page | 5.3 | 18.1 ms | 24.5 ms | 45.3 ms | 0% |
| Author page | 5.28 | 17.9 ms | 22.8 ms | 31.6 ms | 0% |
| RSS feed | 5.28 | 22.4 ms | 31.2 ms | 45.3 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 11.1 | 88.9 ms | 123 ms | 186 ms | 0% |
| Post page | 27.6 | 65.8 ms | 96 ms | 174 ms | 0% |
| Tag page | 5.53 | 58.4 ms | 85.4 ms | 158 ms | 0% |
| Author page | 5.54 | 58.4 ms | 81.5 ms | 150 ms | 0% |
| RSS feed | 5.51 | 64.6 ms | 98.5 ms | 156 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 10.6 | 369 ms | 492 ms | 511 ms | 0% |
| Post page | 26.4 | 311 ms | 432 ms | 461 ms | 0% |
| Tag page | 5.25 | 198 ms | 310 ms | 337 ms | 0% |
| Author page | 5.28 | 193 ms | 285 ms | 306 ms | 0% |
| RSS feed | 5.27 | 209 ms | 308 ms | 331 ms | 0% |

#### Staff in Ghost Admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Post list | 5.34 | 28.1 ms | 46.4 ms | 76.7 ms | 0% |
| Post editor | 16.1 | 10.9 ms | 17.3 ms | 23.4 ms | 0% |
| Saving a draft | 16 | 25.6 ms | 37.2 ms | 63.3 ms | 0% |
| Member list | 5.35 | 30.3 ms | 42.4 ms | 65 ms | 0% |
| 4 virtual users |
| --- |
| Post list | 5.5 | 40 ms | 51.5 ms | 115 ms | 0% |
| Post editor | 16.6 | 22 ms | 33.2 ms | 57 ms | 0% |
| Saving a draft | 16.6 | 180 ms | 249 ms | 312 ms | 0% |
| Member list | 5.52 | 48.6 ms | 62 ms | 105 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 358 MB and MySQL at 579 MB.

### Wagtail

#### Visitors

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 2.36 | 55.7 ms | 60 ms | 66.6 ms | 0% |
| Blog index | 2.36 | 195 ms | 203 ms | 208 ms | 0% |
| Blog post | 7.04 | 17.7 ms | 27.2 ms | 30 ms | 0% |
| Bread page | 7.06 | 19.5 ms | 21.8 ms | 24.9 ms | 0% |
| Location page | 2.36 | 18.5 ms | 20.5 ms | 25 ms | 0% |
| Site search | 2.34 | 28.9 ms | 49.9 ms | 51.2 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 2.21 | 255 ms | 291 ms | 336 ms | 0% |
| Blog index | 2.26 | 845 ms | 912 ms | 1.09 s | 0% |
| Blog post | 6.65 | 72.3 ms | 112 ms | 131 ms | 0% |
| Bread page | 6.69 | 79.8 ms | 98.1 ms | 118 ms | 0% |
| Location page | 2.26 | 76 ms | 91.1 ms | 96.2 ms | 0% |
| Site search | 2.22 | 114 ms | 208 ms | 229 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 2.13 | 869 ms | 1.19 s | 1.46 s | 0% |
| Blog index | 2.23 | 2.09 s | 2.59 s | 2.73 s | 0% |
| Blog post | 6.42 | 480 ms | 863 ms | 1.04 s | 0% |
| Bread page | 6.45 | 487 ms | 835 ms | 1.09 s | 0% |
| Location page | 2.18 | 472 ms | 884 ms | 1.06 s | 0% |
| Site search | 2.12 | 574 ms | 945 ms | 1.03 s | 0% |

#### Editors in the Wagtail admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Admin dashboard | 0.962 | 57.5 ms | 62.8 ms | 72.5 ms | 0% |
| Page explorer | 1.96 | 247 ms | 260 ms | 375 ms | 0% |
| Page editor | 2.94 | 117 ms | 147 ms | 227 ms | 0% |
| Image library | 0.978 | 45.2 ms | 48.7 ms | 298 ms | 0% |
| Admin page search | 0.978 | 23.1 ms | 51.3 ms | 51.9 ms | 0% |
| 4 virtual users |
| --- |
| Admin dashboard | 0.876 | 317 ms | 453 ms | 590 ms | 0% |
| Page explorer | 1.77 | 1.14 s | 1.43 s | 1.47 s | 0% |
| Page editor | 2.69 | 538 ms | 731 ms | 892 ms | 0% |
| Image library | 0.892 | 270 ms | 450 ms | 464 ms | 0% |
| Admin page search | 0.876 | 120 ms | 288 ms | 388 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 296 MB, Postgres at 181 MB, and Redis at 26 MB.

## 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:** Los Angeles, 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, 18:40:51 UTC

**Parser version:** 5

## Run timeline

**Queued:** Oct 11, 2026, 18:37:00 UTC

**Server created:** Oct 11, 2026, 18:38:09 UTC

**First update from the server:** Oct 11, 2026, 18:38:09 UTC

**Completed:** Oct 11, 2026, 20:08:47 UTC

**Server deleted:** Oct 11, 2026, 20:08:47 UTC

**Cost of this run:** $0.058

Tests 59 of 59 done Live output 794 lines

Setup 1 cores, 1.9 GiB RAM 4 of 4Done

Disk (fio) 346 MB/s at 4k, 5.47 GB/s at 1m 5 of 5Done

Network, IPv4 (iperf3) Median 5.57 Gbit/s send, 7.59 Gbit/s receive, 1 retried 5 of 5Done

Geekbench 7, single-core Score 1,762 18 of 18Done

Phoronix (memory, TLS, scheduler) 3 of 3Done

Datastores 5 of 5Done

Web frameworks 18 of 18Done

Finish Results saved 1 of 1Done

Watch party 0 watching

This party closed at 19:47 UTC. It's read only now.

## Watch party

Loading the party