# Vultr CPU Optimized AMD 1 vCPU / 2 GB

[Amsterdam, NL](https://rackcensus.com/locations/amsterdam-vps-benchmarks "Every provider in Amsterdam")

Benchmark complete

Finished Oct 12, 2026

Geekbench 7 single-core

1,623

Geekbench 7 multi-core

Skipped

Disk 4K IOPS

83,166

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=ams)

-

Provider

Vultr

-

Plan

CPU Optimized AMD 1 vCPU / 2 GB

-

Location

Amsterdam, NL

-

vCPU

1

-

RAM

2 GB

-

Storage

25 GB NVMe

-

Network

Unknown

-

OS image

2284

-

Trigger

Manual

-

Queued at

Oct 12, 2026, 01:06:45 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

- [Los Angeles, US Oct 11, 2026](https://rackcensus.com/benchmarks/2m35m1-vultr-cpu-optimized-amd-1-vcpu-2-gb-lax-benchmark)1,762
- [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,623 | Skipped | [Geekbench Browser](https://browser.geekbench.com/v7/cpu/610590) |

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,69526th of 106 | Single-core only |
| Navigation | 1,51836th of 106 | Single-core only |
| HTML5 Browser | 1,70020th of 106 | Single-core only |
| PDF Viewer | 1,59132nd of 106 | Single-core only |
| Photo Library | 1,7459th of 106 | Single-core only |
| Clang | 1,46124th of 106 | Single-core only |
| Text Processing | 1,51024th of 106 | Single-core only |
| Asset Compression | 1,67426th of 106 | Single-core only |
| HDR | 1,64029th of 106 | Single-core only |
| Photo Editor | 2,04317th of 106 | Single-core only |
| Ray Tracer | 1,45032nd of 106 | Single-core only |
| Structure from Motion | 1,58144th of 106 | Single-core only |
| Game Physics | 1,58323rd of 106 | Single-core only |
| Video Encoder | 1,52928th of 106 | Single-core only |
| Audio Encoder | 1,69225th of 106 | Single-core only |
| Video Player | 1,64634th 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 | 30.3 GB/s | 3 | 2.22% |
| Scale higher is better | 40.7 GB/s | 3 | 5.59% |
| Add higher is better | 27.4 GB/s | 3 | 1.3% |
| Triad higher is better | 28.2 GB/s | 3 | 3.47% |

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 | 697/s | 3 | 1.67% |
| RSA 4096 verifies higher is better | 12,127/s | 3 | 2.8% |
| SHA-256 higher is better | 1.07 GB/s | 3 | 0.743% |
| AES-256-GCM higher is better | 10.7 GB/s | 3 | 1.32% |
| ChaCha20-Poly1305 higher is better | 4.09 GB/s | 3 | 0.594% |

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.77 ms | 3 | 0.324% |
| Requests per second, 90th percentile higher is better | 263/s | 3 | 0.58% |
| Request latency, 99.9th percentile lower is better | 7.24 ms | 3 | 2.47% |
| Requests per second, average higher is better | 259/s | 3 | 0.424% |

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

## Disk

| Block size | Read | Write | Total |
| --- | --- | --- | --- |
| 4K | 162.2 MB/s (41,528 IOPS) | 162.7 MB/s (41,638 IOPS) | 324.9 MB/s (83,166 IOPS) |
| 64K | 1.16 GB/s (19,078 IOPS) | 1.17 GB/s (19,179 IOPS) | 2.34 GB/s (38,257 IOPS) |
| 512K | 1.3 GB/s (2,656 IOPS) | 1.37 GB/s (2,797 IOPS) | 2.66 GB/s (5,453 IOPS) |
| 1M | 1.36 GB/s (1,393 IOPS) | 1.45 GB/s (1,486 IOPS) | 2.81 GB/s (2,879 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 | 8.29 Gbps | 5.38 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 7.79 Gbps | 9.28 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 1.68 Gbps | 6.32 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 976 Mbps | 1.53 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 5.97 Gbps | 6.68 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 | 13,067 | 0.077 ms |
| fdatasync | 11,713 | 0.085 ms |
| fsync | 9,822 | 0.102 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 10,443 | 0.096 ms |
| Two 8 kB writes |
| --- |
| open\_datasync | 6,362 | 0.157 ms |
| fdatasync | 11,068 | 0.09 ms |
| fsync | 9,359 | 0.107 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 5,213 | 0.192 ms |
| open\_sync at different write sizes |
| --- |
| 1 \* 16kB open\_sync write | 9,583 | 0.104 ms |
| 2 \* 8kB open\_sync writes | 5,421 | 0.184 ms |
| 4 \* 4kB open\_sync writes | 2,608 | 0.383 ms |
| 8 \* 2kB open\_sync writes | 1,020 | 0.98 ms |
| 16 \* 1kB open\_sync writes | 505 | 1.98 ms |
| fsync on a non-write descriptor |
| --- |
| write, fsync, close | 8,498 | 0.118 ms |
| write, close, fsync | 8,522 | 0.117 ms |
| Non-synced 8 kB writes |
| --- |
| write | 577,353 | 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,128 | 0.307 ms | 0.38 ms | 0.497 ms | 1.44 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,477 | 2.15 ms | 3.36 ms | 4.36 ms | 6.24 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,066 | 8.84 ms | 20.5 ms | 32.1 ms | 52.5 ms | 0 |
| Read only | 1 | 37,477 | 0.024 ms | 0.039 ms | 0.051 ms | 0.083 ms | 0 |
| Read only | 8 | 36,311 | 0.183 ms | 0.32 ms | 0.402 ms | 0.713 ms | 0 |
| Read only | 32 | 34,956 | 0.76 ms | 1.29 ms | 1.52 ms | 2.11 ms | 0 |

Scale 10 (1,000,000 accounts), loaded in 1.2 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,848 | 0.514 ms | 0.709 ms | 1.3 ms | 2.11 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,630 | 2.86 ms | 4.48 ms | 5.9 ms | 8.02 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,776 | 10.7 ms | 16.6 ms | 21.4 ms | 32.9 ms | 0 |
| Read only | 1 | 8,151 | 0.147 ms | 0.225 ms | 0.413 ms | 1.34 ms | 0 |
| Read only | 8 | 20,672 | 0.287 ms | 0.759 ms | 1.22 ms | 2.14 ms | 0 |
| Read only | 32 | 20,852 | 1.29 ms | 1.91 ms | 2.97 ms | 4.24 ms | 0 |

Scale 100 (10,000,000 accounts), loaded in 13.4 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 | 547 | 10,942 | 1.7 ms | 2.66 ms | 4.65 ms | 0 |
| Read/write | 8 | 609 | 12,190 | 12.1 ms | 20.4 ms | 31.4 ms | 0 |
| Read/write | 32 | 623 | 12,466 | 46.6 ms | 87.6 ms | 119 ms | 0 |
| Read only | 1 | 1,378 | 22,046 | 0.69 ms | 0.904 ms | 1.3 ms | 0 |
| Read only | 8 | 1,253 | 20,050 | 6.32 ms | 7.7 ms | 8.74 ms | 0 |
| Read only | 32 | 1,146 | 18,331 | 27.7 ms | 33.7 ms | 37.6 ms | 0 |

10 tables of 100,000 rows, loaded in 9.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 | 38,624 | 35,112 | 1.58 ms | 3.07 ms | 4.22 ms |
| 1:1 set:get | 38,240 | 19,120 | 1.6 ms | 3.1 ms | 4.29 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 | 422 | 1,435 | 2,121 | 1.02 s |
| Express express-postgresjs | 4,482 | 6,667 | 22,030 | 829 ms |
| Fastify fastify-postgres | 4,348 | 6,976 | 24,919 | 998 ms |
| NestJS nestjs | 3,143 | 3,424 | 12,672 | 141 ms |
| Nuxt nuxt | 3,928 | 6,858 | 22,105 | 1.31 s |
| FastAPI fastapi | 2,410 | 2,957 | 14,684 | 521 ms |
| Django django-postgresql | 1,171 | 1,278 | 3,022 | 255 ms |
| Rails rails | 1,904 | 2,679 | 9,861 | 152 ms |
| Laravel laravel | 525 | 564 | 992 | 521 ms |
| Symfony symfony | 626 | 676 | 1,857 | 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.52 | 989 ms | 1.09 s | 1.14 s | 0% |
| Shop page | 1.52 | 1.28 s | 1.46 s | 1.52 s | 0% |
| Category page | 1.52 | 1.07 s | 1.37 s | 1.46 s | 0% |
| Product page | 1.52 | 972 ms | 1.15 s | 1.21 s | 0% |
| Product search | 1.52 | 875 ms | 990 ms | 1.05 s | 0% |
| 32 virtual users |
| --- |
| Home page | 1.53 | 3.71 s | 4.26 s | 4.34 s | 0% |
| Shop page | 1.53 | 4.85 s | 5.76 s | 5.89 s | 0% |
| Category page | 1.53 | 4.42 s | 5.47 s | 5.62 s | 0% |
| Product page | 1.53 | 3.9 s | 4.2 s | 4.28 s | 0% |
| Product search | 1.53 | 3.63 s | 3.97 s | 4.08 s | 0% |

#### Cart and checkout

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 8 virtual users |
| --- |
| Add to cart | 3.11 | 960 ms | 1.11 s | 1.16 s | 0% |
| Cart | 3.11 | 883 ms | 994 ms | 1.04 s | 0% |
| Checkout | 3.11 | 716 ms | 867 ms | 916 ms | 0% |
| 32 virtual users |
| --- |
| Add to cart | 2.96 | 3.62 s | 4.45 s | 4.6 s | 0% |
| Cart | 2.96 | 3.96 s | 4.39 s | 4.46 s | 0% |
| Checkout | 2.96 | 3.1 s | 3.58 s | 3.76 s | 0% |

k6 with a fixed number of virtual users, 62 to 68 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.72 | 160 ms | 274 ms | 373 ms | 0% |
| Topic JSON | 1.36 | 77.9 ms | 159 ms | 230 ms | 0% |
| Home page | 1.38 | 141 ms | 196 ms | 318 ms | 0% |
| Categories page | 0.679 | 162 ms | 179 ms | 209 ms | 0% |
| User activity page | 0.679 | 99 ms | 140 ms | 245 ms | 0% |
| 4 virtual users |
| --- |
| Topic page | 2.08 | 827 ms | 1.17 s | 2.21 s | 0% |
| Topic JSON | 1.03 | 420 ms | 521 ms | 626 ms | 0% |
| Home page | 1.03 | 743 ms | 1.57 s | 2.35 s | 0% |
| Categories page | 0.539 | 868 ms | 1.03 s | 1.1 s | 0% |
| User activity page | 0.523 | 543 ms | 762 ms | 971 ms | 0% |
| 16 virtual users |
| --- |
| Topic page | 2.3 | 1.93 s | 2.41 s | 2.92 s | 0% |
| Topic JSON | 1.16 | 1.57 s | 1.87 s | 2.01 s | 0% |
| Home page | 1.15 | 1.84 s | 2.35 s | 3.22 s | 0% |
| Categories page | 0.566 | 1.92 s | 2.52 s | 2.75 s | 0% |
| User activity page | 0.582 | 1.64 s | 2.02 s | 2.06 s | 0% |

#### Anonymous

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 16 virtual users |
| --- |
| Topic page | 46.7 | 92.1 ms | 232 ms | 359 ms | 0% |
| Topic JSON | 23.3 | 91.8 ms | 234 ms | 341 ms | 0% |
| Home page | 23.3 | 98.5 ms | 236 ms | 301 ms | 0% |
| Categories page | 11.7 | 89.3 ms | 223 ms | 316 ms | 0% |
| User activity page | 11.7 | 294 ms | 502 ms | 806 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. 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 315 MB of it. The container peaked at 1,466 MB.

### Ghost

#### Readers

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 9.32 | 27.9 ms | 37.3 ms | 67 ms | 0% |
| Post page | 23.3 | 15.6 ms | 24.4 ms | 42.1 ms | 0% |
| Tag page | 4.66 | 20.5 ms | 27.4 ms | 31.8 ms | 0% |
| Author page | 4.66 | 20.3 ms | 26.1 ms | 47.7 ms | 0% |
| RSS feed | 4.64 | 24.4 ms | 38.6 ms | 86.9 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 9.77 | 101 ms | 138 ms | 209 ms | 0% |
| Post page | 24.4 | 74.4 ms | 114 ms | 190 ms | 0% |
| Tag page | 4.91 | 65.6 ms | 93.2 ms | 167 ms | 0% |
| Author page | 4.88 | 65.9 ms | 96.7 ms | 157 ms | 0% |
| RSS feed | 4.86 | 74.5 ms | 103 ms | 160 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 9.5 | 417 ms | 546 ms | 583 ms | 0% |
| Post page | 23.7 | 347 ms | 473 ms | 511 ms | 0% |
| Tag page | 4.74 | 227 ms | 337 ms | 370 ms | 0% |
| Author page | 4.74 | 230 ms | 338 ms | 370 ms | 0% |
| RSS feed | 4.76 | 228 ms | 336 ms | 363 ms | 0% |

#### Staff in Ghost Admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Post list | 4.9 | 30.8 ms | 53.2 ms | 75.5 ms | 0% |
| Post editor | 14.7 | 12.1 ms | 18.9 ms | 25.2 ms | 0% |
| Saving a draft | 14.7 | 27.7 ms | 39.2 ms | 89.1 ms | 0% |
| Member list | 4.92 | 33.6 ms | 47.6 ms | 59.8 ms | 0% |
| 4 virtual users |
| --- |
| Post list | 4.98 | 47.1 ms | 63.8 ms | 149 ms | 0% |
| Post editor | 15 | 24.8 ms | 34.9 ms | 70.5 ms | 0% |
| Saving a draft | 15 | 196 ms | 273 ms | 336 ms | 0% |
| Member list | 5.02 | 49.8 ms | 66.8 ms | 88.9 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 351 MB and MySQL at 577 MB.

### Wagtail

#### Visitors

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 2.35 | 56 ms | 64.3 ms | 78.9 ms | 0% |
| Blog index | 2.35 | 192 ms | 210 ms | 219 ms | 0% |
| Blog post | 7.03 | 18 ms | 27.5 ms | 31 ms | 0% |
| Bread page | 7.04 | 19.9 ms | 22.5 ms | 25.8 ms | 0% |
| Location page | 2.35 | 18.9 ms | 21.5 ms | 24.1 ms | 0% |
| Site search | 2.35 | 30.2 ms | 50.5 ms | 53.2 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 2.15 | 263 ms | 310 ms | 394 ms | 0% |
| Blog index | 2.19 | 854 ms | 1.01 s | 1.12 s | 0% |
| Blog post | 6.5 | 73.6 ms | 120 ms | 148 ms | 0% |
| Bread page | 6.51 | 82.8 ms | 100 ms | 112 ms | 0% |
| Location page | 2.2 | 79.1 ms | 97.2 ms | 119 ms | 0% |
| Site search | 2.15 | 120 ms | 204 ms | 235 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 2.04 | 924 ms | 1.37 s | 1.59 s | 0% |
| Blog index | 2.08 | 2.23 s | 2.74 s | 3.07 s | 0% |
| Blog post | 6.1 | 506 ms | 887 ms | 1.35 s | 0% |
| Bread page | 6.13 | 514 ms | 846 ms | 1.43 s | 0% |
| Location page | 2.06 | 486 ms | 1.02 s | 1.33 s | 0% |
| Site search | 2.03 | 620 ms | 983 ms | 1.14 s | 0% |

#### Editors in the Wagtail admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Admin dashboard | 0.929 | 60.1 ms | 71.7 ms | 81.6 ms | 0% |
| Page explorer | 1.86 | 256 ms | 301 ms | 397 ms | 0% |
| Page editor | 2.79 | 123 ms | 159 ms | 231 ms | 0% |
| Image library | 0.929 | 46.7 ms | 52 ms | 334 ms | 0% |
| Admin page search | 0.929 | 25.3 ms | 57.3 ms | 78 ms | 0% |
| 4 virtual users |
| --- |
| Admin dashboard | 0.825 | 323 ms | 511 ms | 649 ms | 0% |
| Page explorer | 1.67 | 1.14 s | 1.49 s | 1.56 s | 0% |
| Page editor | 2.52 | 562 ms | 764 ms | 886 ms | 0% |
| Image library | 0.842 | 334 ms | 459 ms | 535 ms | 0% |
| Admin page search | 0.825 | 130 ms | 232 ms | 363 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 295 MB, Postgres at 175 MB, and Redis at 26 MB.

## Advertised vs. measured

| Spec | Advertised | Measured |
| --- | --- | --- |
| vCPU | 1 | 1 |
| CPU | Dedicated vCPU | 0.1% 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-Genoa Processor

**CPU cores:** 1

**CPU frequency:** 2900 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.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:** CPU Optimized AMD 1 vCPU / 2 GB

**Product line:** Optimized Cloud CPU

**Location:** Amsterdam, NL

**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 12, 2026, 01:56:21 UTC

**Parser version:** 5

## Run timeline

**Queued:** Oct 12, 2026, 01:06:45 UTC

**Server created:** Oct 12, 2026, 01:54:04 UTC

**First update from the server:** Oct 12, 2026, 01:54:04 UTC

**Completed:** Oct 12, 2026, 03:25:14 UTC

**Server deleted:** Oct 12, 2026, 03:25:14 UTC

**Cost of this run:** $0.058

Tests 59 of 59 done Live output 816 lines

Setup 1 cores, 1.9 GiB RAM 4 of 4Done

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

Network, IPv4 (iperf3) Median 5.97 Gbit/s send, 6.32 Gbit/s receive, 3 retried 5 of 5Done

Geekbench 7, single-core Score 1,623 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 04:25 UTC. It's read only now.

## Watch party

Loading the party