# Vultr High Frequency Intel 2 vCPU / 2 GB

[Chicago, US](https://rackcensus.com/locations/chicago-vps-benchmarks "Every provider in Chicago")

Benchmark complete

Finished Oct 16, 2026

Geekbench 7 single-core

1,244

Faster than 58% of 2 vCPU plans

Geekbench 7 multi-core

Skipped

Disk 4K IOPS

202,505

fio random read and write, 50/50

Monthly price at test time

$18.00

Same price today

## Server

[Vultr](https://rackcensus.com/vps-providers/vultr-benchmarks)[High Frequency Intel 2 vCPU / 2 GB](https://rackcensus.com/plans/1n3gtj-vultr-high-frequency-intel-2-vcpu-2-gb-benchmarks?location=ord)

-

Provider

Vultr

-

Plan

High Frequency Intel 2 vCPU / 2 GB

-

Location

Chicago, US

-

vCPU

2

-

RAM

2 GB

-

Storage

80 GB NVMe

-

Network

Unknown

-

OS image

2284

-

Trigger

Scheduled

-

Queued at

Oct 16, 2026, 14:32: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

- [New Jersey, US Oct 15, 2026](https://rackcensus.com/benchmarks/z1d6mv-vultr-high-frequency-intel-2-vcpu-2-gb-ewr-benchmark)1,508
- [Seattle, US Oct 14, 2026](https://rackcensus.com/benchmarks/z451eh-vultr-high-frequency-intel-2-vcpu-2-gb-sea-benchmark)1,529

[Full history of this plan](https://rackcensus.com/plans/1n3gtj-vultr-high-frequency-intel-2-vcpu-2-gb-benchmarks/history)

## CPU

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

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 | 1,193116th of 217 | Single-core only |
| Navigation | 1,51159th of 217 | Single-core only |
| HTML5 Browser | 1,186103rd of 217 | Single-core only |
| PDF Viewer | 1,35795th of 217 | Single-core only |
| Photo Library | 1,016121st of 217 | Single-core only |
| Clang | 1,17583rd of 217 | Single-core only |
| Text Processing | 1,20489th of 217 | Single-core only |
| Asset Compression | 1,036146th of 217 | Single-core only |
| HDR | 1,142101st of 217 | Single-core only |
| Photo Editor | 1,41797th of 217 | Single-core only |
| Ray Tracer | 1,26693rd of 217 | Single-core only |
| Structure from Motion | 1,46386th of 217 | Single-core only |
| Game Physics | 1,158115th of 217 | Single-core only |
| Video Encoder | 1,24783rd of 217 | Single-core only |
| Audio Encoder | 1,289100th of 217 | Single-core only |
| Video Player | 1,37296th of 217 | Single-core only |

Rank among the 217 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.5 GB/s | 3 | 4.59% |
| Scale higher is better | 20.3 GB/s | 3 | 7.03% |
| Add higher is better | 21.9 GB/s | 3 | 5.99% |
| Triad higher is better | 21.9 GB/s | 3 | 5% |

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 | 327/s | 3 | 1.53% |
| RSA 4096 verifies higher is better | 21,127/s | 3 | 1.27% |
| SHA-256 higher is better | 591 MB/s | 3 | 0.164% |
| AES-256-GCM higher is better | 7.98 GB/s | 3 | 0.586% |
| ChaCha20-Poly1305 higher is better | 4.29 GB/s | 3 | 0.354% |

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.55 ms | 3 | 0.26% |
| Requests per second, 90th percentile higher is better | 540/s | 3 | 1.54% |
| Request latency, 99.9th percentile lower is better | 8.23 ms | 3 | 12.2% |
| Requests per second, average higher is better | 525/s | 3 | 1.53% |

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

## Disk

| Block size | Read | Write | Total |
| --- | --- | --- | --- |
| 4K | 395 MB/s (101,119 IOPS) | 396 MB/s (101,386 IOPS) | 791 MB/s (202,505 IOPS) |
| 64K | 550.7 MB/s (8,811 IOPS) | 553.6 MB/s (8,857 IOPS) | 1.08 GB/s (17,668 IOPS) |
| 512K | 619 MB/s (1,237 IOPS) | 651.9 MB/s (1,303 IOPS) | 1.24 GB/s (2,540 IOPS) |
| 1M | 659.8 MB/s (659 IOPS) | 703.7 MB/s (703 IOPS) | 1.33 GB/s (1,362 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.02 Gbps | 2.28 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 5.63 Gbps | 13.6 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 2.08 Gbps | 5.17 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 3.86 Gbps | 4.5 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 8.63 Gbps | 9.3 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 | 12,328 | 0.081 ms |
| fdatasync | 11,288 | 0.089 ms |
| fsync | 9,393 | 0.106 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 10,778 | 0.093 ms |
| Two 8 kB writes |
| --- |
| open\_datasync | 5,974 | 0.167 ms |
| fdatasync | 10,186 | 0.098 ms |
| fsync | 9,726 | 0.103 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 5,636 | 0.177 ms |
| open\_sync at different write sizes |
| --- |
| 1 \* 16kB open\_sync write | 9,230 | 0.108 ms |
| 2 \* 8kB open\_sync writes | 4,785 | 0.209 ms |
| 4 \* 4kB open\_sync writes | 2,345 | 0.426 ms |
| 8 \* 2kB open\_sync writes | 1,220 | 0.819 ms |
| 16 \* 1kB open\_sync writes | 637 | 1.57 ms |
| fsync on a non-write descriptor |
| --- |
| write, fsync, close | 7,660 | 0.131 ms |
| write, close, fsync | 7,787 | 0.128 ms |
| Non-synced 8 kB writes |
| --- |
| write | 831,343 | 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,359 | 0.414 ms | 0.511 ms | 0.584 ms | 1.38 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,586 | 1.65 ms | 2.68 ms | 3.5 ms | 4.95 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,374 | 5.89 ms | 16.7 ms | 27.5 ms | 45.3 ms | 0 |
| Read only | 1 | 24,735 | 0.037 ms | 0.051 ms | 0.061 ms | 0.084 ms | 0 |
| Read only | 8 | 44,029 | 0.168 ms | 0.265 ms | 0.315 ms | 0.536 ms | 0 |
| Read only | 32 | 46,439 | 0.624 ms | 0.948 ms | 1.25 ms | 2.03 ms | 0 |

Scale 10 (1,000,000 accounts), loaded in 1.28 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,684 | 0.579 ms | 0.798 ms | 1.02 ms | 2.13 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,248 | 1.84 ms | 2.6 ms | 3.62 ms | 5.75 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,408 | 6.96 ms | 10.7 ms | 13.7 ms | 18.9 ms | 0 |
| Read only | 1 | 7,354 | 0.081 ms | 0.283 ms | 0.418 ms | 0.993 ms | 0 |
| Read only | 8 | 29,450 | 0.23 ms | 0.536 ms | 0.71 ms | 2.17 ms | 0 |
| Read only | 32 | 30,053 | 0.913 ms | 1.82 ms | 2.6 ms | 4.54 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 | 427 | 8,546 | 2.22 ms | 3.08 ms | 4.65 ms | 0 |
| Read/write | 8 | 870 | 17,399 | 9.06 ms | 13.5 ms | 17 ms | 0 |
| Read/write | 32 | 896 | 17,917 | 34.3 ms | 60 ms | 77.2 ms | 0 |
| Read only | 1 | 968 | 15,483 | 1.01 ms | 1.23 ms | 1.5 ms | 0 |
| Read only | 8 | 1,626 | 26,013 | 4.74 ms | 6.67 ms | 7.7 ms | 0 |
| Read only | 32 | 1,558 | 24,930 | 20 ms | 25.7 ms | 28.7 ms | 0 |

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

### Redis

#### memtier

| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
| --- | --- | --- | --- | --- | --- |
| 1:10 set:get | 83,337 | 75,761 | 0.607 ms | 2.08 ms | 2.72 ms |
| 1:1 set:get | 80,477 | 40,238 | 0.623 ms | 2.24 ms | 2.94 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 | 550 | 2,008 | 2,964 | 693 ms |
| Express express-postgresjs | 6,812 | 9,801 | 27,152 | 71.1 ms |
| Fastify fastify-postgres | 6,659 | 10,398 | 28,754 | 66.9 ms |
| NestJS nestjs | 4,199 | 4,877 | 16,173 | 143 ms |
| Nuxt nuxt | 5,550 | 9,055 | 25,090 | 95.8 ms |
| FastAPI fastapi | 3,400 | 4,235 | 17,013 | 266 ms |
| Django django-postgresql | 1,773 | 2,004 | 4,339 | 280 ms |
| Rails rails | 2,719 | 3,922 | 14,079 | 142 ms |
| Laravel laravel | 755 | 765 | 1,483 | 370 ms |
| Symfony symfony | 992 | 1,049 | 2,773 | 281 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.

## Web apps

### WooCommerce

#### Page mix

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 8 virtual users |
| --- |
| Home page | 2.23 | 704 ms | 836 ms | 1.06 s | 0% |
| Shop page | 2.23 | 974 ms | 1.11 s | 1.25 s | 0% |
| Category page | 2.23 | 592 ms | 1.01 s | 1.11 s | 0% |
| Product page | 2.23 | 649 ms | 791 ms | 825 ms | 0% |
| Product search | 2.23 | 558 ms | 684 ms | 717 ms | 0% |
| 32 virtual users |
| --- |
| Home page | 2.27 | 2.68 s | 3.1 s | 3.19 s | 0% |
| Shop page | 2.27 | 3.54 s | 4.06 s | 4.16 s | 0% |
| Category page | 2.27 | 3.05 s | 3.65 s | 3.8 s | 0% |
| Product page | 2.25 | 2.63 s | 2.87 s | 2.99 s | 0% |
| Product search | 1.88 | 2.46 s | 2.93 s | 2.95 s | 0% |

#### Cart and checkout

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 8 virtual users |
| --- |
| Add to cart | 4.29 | 769 ms | 895 ms | 933 ms | 0% |
| Cart | 4.29 | 612 ms | 722 ms | 741 ms | 0% |
| Checkout | 4.29 | 463 ms | 550 ms | 563 ms | 0% |
| 32 virtual users |
| --- |
| Add to cart | 4.31 | 2.57 s | 3.1 s | 3.2 s | 0% |
| Cart | 4.31 | 2.67 s | 2.99 s | 3.1 s | 0% |
| Checkout | 4.31 | 2.1 s | 2.44 s | 2.51 s | 0% |

k6 with a fixed number of virtual users, 62 to 71 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.12 | 206 ms | 280 ms | 387 ms | 0% |
| Topic JSON | 1.06 | 107 ms | 133 ms | 188 ms | 0% |
| Home page | 1.06 | 184 ms | 270 ms | 428 ms | 0% |
| Categories page | 0.529 | 215 ms | 277 ms | 428 ms | 0% |
| User activity page | 0.529 | 125 ms | 184 ms | 305 ms | 0% |
| 4 virtual users |
| --- |
| Topic page | 3.72 | 479 ms | 657 ms | 776 ms | 0% |
| Topic JSON | 1.86 | 256 ms | 338 ms | 424 ms | 0% |
| Home page | 1.86 | 428 ms | 559 ms | 652 ms | 0% |
| Categories page | 0.922 | 485 ms | 621 ms | 695 ms | 0% |
| User activity page | 0.922 | 298 ms | 608 ms | 709 ms | 0% |
| 16 virtual users |
| --- |
| Topic page | 3.78 | 1.55 s | 1.86 s | 2.05 s | 0% |
| Topic JSON | 1.92 | 1.34 s | 1.59 s | 1.71 s | 0% |
| Home page | 1.87 | 1.48 s | 1.74 s | 1.81 s | 0% |
| Categories page | 0.942 | 1.57 s | 1.92 s | 2.06 s | 0% |
| User activity page | 0.926 | 1.33 s | 1.58 s | 1.68 s | 0% |

#### Anonymous

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 16 virtual users |
| --- |
| Topic page | 72.1 | 62.2 ms | 153 ms | 181 ms | 0% |
| Topic JSON | 36.1 | 59.6 ms | 151 ms | 186 ms | 0% |
| Home page | 36 | 59.3 ms | 146 ms | 182 ms | 0% |
| Categories page | 18 | 64.3 ms | 161 ms | 205 ms | 0% |
| User activity page | 18.1 | 197 ms | 319 ms | 397 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 364 MB of it. The container peaked at 1,446 MB.

### Ghost

#### Readers

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 8.21 | 34.8 ms | 38.5 ms | 50 ms | 0% |
| Post page | 20.5 | 18.2 ms | 22 ms | 30.8 ms | 0% |
| Tag page | 4.11 | 24.1 ms | 28 ms | 38.4 ms | 0% |
| Author page | 4.1 | 23.7 ms | 26.2 ms | 32 ms | 0% |
| RSS feed | 4.1 | 29.9 ms | 33.5 ms | 41.2 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 9.29 | 112 ms | 150 ms | 186 ms | 0% |
| Post page | 23.2 | 78.7 ms | 112 ms | 137 ms | 0% |
| Tag page | 4.64 | 72.2 ms | 101 ms | 130 ms | 0% |
| Author page | 4.64 | 73.7 ms | 99.9 ms | 127 ms | 0% |
| RSS feed | 4.63 | 77.5 ms | 113 ms | 147 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 9.35 | 431 ms | 525 ms | 569 ms | 0% |
| Post page | 23.5 | 354 ms | 442 ms | 484 ms | 0% |
| Tag page | 4.68 | 235 ms | 311 ms | 358 ms | 0% |
| Author page | 4.7 | 237 ms | 315 ms | 354 ms | 0% |
| RSS feed | 4.68 | 237 ms | 320 ms | 352 ms | 0% |

#### Staff in Ghost Admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Post list | 4.6 | 33.1 ms | 44.6 ms | 56.6 ms | 0% |
| Post editor | 13.9 | 12.6 ms | 17.2 ms | 28.5 ms | 0% |
| Saving a draft | 13.9 | 30.5 ms | 39.1 ms | 49.8 ms | 0% |
| Member list | 4.62 | 40 ms | 48.5 ms | 60.6 ms | 0% |
| 4 virtual users |
| --- |
| Post list | 5.12 | 47.2 ms | 61.2 ms | 93.2 ms | 0% |
| Post editor | 15.4 | 25.5 ms | 35 ms | 55.7 ms | 0% |
| Saving a draft | 15.4 | 190 ms | 254 ms | 301 ms | 0% |
| Member list | 5.16 | 58.6 ms | 71.2 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 355 MB and MySQL at 575 MB.

### Wagtail

#### Visitors

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 1.56 | 83.7 ms | 94.8 ms | 103 ms | 0% |
| Blog index | 1.56 | 288 ms | 340 ms | 369 ms | 0% |
| Blog post | 4.67 | 26.7 ms | 41.7 ms | 46.1 ms | 0% |
| Bread page | 4.69 | 29.2 ms | 33.8 ms | 37.8 ms | 0% |
| Location page | 1.56 | 28 ms | 32.9 ms | 36.5 ms | 0% |
| Site search | 1.56 | 44.9 ms | 77 ms | 83.5 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 2.88 | 205 ms | 275 ms | 305 ms | 0% |
| Blog index | 2.89 | 663 ms | 896 ms | 947 ms | 0% |
| Blog post | 8.67 | 59.6 ms | 92.5 ms | 126 ms | 0% |
| Bread page | 8.65 | 63.2 ms | 88.5 ms | 97.6 ms | 0% |
| Location page | 2.91 | 60.5 ms | 81.6 ms | 90.5 ms | 0% |
| Site search | 2.88 | 84.7 ms | 175 ms | 211 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 2.95 | 630 ms | 842 ms | 905 ms | 0% |
| Blog index | 3.03 | 1.55 s | 1.78 s | 1.83 s | 0% |
| Blog post | 8.87 | 362 ms | 547 ms | 624 ms | 0% |
| Bread page | 8.87 | 379 ms | 553 ms | 687 ms | 0% |
| Location page | 2.98 | 379 ms | 558 ms | 665 ms | 0% |
| Site search | 2.93 | 442 ms | 596 ms | 702 ms | 0% |

#### Editors in the Wagtail admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Admin dashboard | 0.625 | 86.6 ms | 115 ms | 133 ms | 0% |
| Page explorer | 1.27 | 373 ms | 459 ms | 511 ms | 0% |
| Page editor | 1.89 | 171 ms | 245 ms | 322 ms | 0% |
| Image library | 0.625 | 65.4 ms | 102 ms | 626 ms | 0% |
| Admin page search | 0.625 | 36.3 ms | 86.9 ms | 135 ms | 0% |
| 4 virtual users |
| --- |
| Admin dashboard | 1.07 | 229 ms | 450 ms | 525 ms | 0% |
| Page explorer | 2.18 | 863 ms | 1.4 s | 1.57 s | 0% |
| Page editor | 3.28 | 394 ms | 693 ms | 811 ms | 0% |
| Image library | 1.1 | 207 ms | 471 ms | 554 ms | 0% |
| Admin page search | 1.07 | 97.7 ms | 264 ms | 305 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 297 MB, Postgres at 176 MB, and Redis at 26 MB.

## Advertised vs. measured

| Spec | Advertised | Measured |
| --- | --- | --- |
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 80 GB NVMe | 75 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:** 2

**CPU frequency:** 3696 MHz

**AES-NI:** Yes

**VM-x/AMD-V:** No

**RAM reported:** 1.9 GiB

**Swap reported:** 7.7 GiB

**Disk reported:** 75 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:** High Frequency Intel 2 vCPU / 2 GB

**Product line:** Cloud Compute High Frequency

**Location:** Chicago, US

**vCPU:** 2 shared vCPU

**Architecture:** x86\_64

**RAM:** 2 GB

**Storage:** 80 GB NVMe

**Virtualization:** KVM

**Network:** Unknown

**Transfer:** 3.07 TB

**Port 25:** On request

**Monthly price at test time:** $18.00

**Hourly price at test time:** $0.025

**YABS version:** v2026-09-20

**Ran at:** Oct 16, 2026, 14:33:02 UTC

**Parser version:** 5

## Run timeline

**Queued:** Oct 16, 2026, 14:32:00 UTC

**Server created:** Oct 16, 2026, 14:32:56 UTC

**First update from the server:** Oct 16, 2026, 14:32:59 UTC

**Completed:** Oct 16, 2026, 16:01:22 UTC

**Server deleted:** Oct 16, 2026, 16:01:22 UTC

**Cost of this run:** $0.037

Tests 59 of 59 done Live output 802 lines

Setup 2 cores, 1.9 GiB RAM 4 of 4Done

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

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

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

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

Datastores 5 of 5Done

Web frameworks 10 of 10Done

Web apps 8 of 8Done

Finish Results saved 1 of 1Done

Watch party 0 watching

This party closed at 17:01 UTC. It's read only now.

## Watch party

Loading the party