# Vultr High Frequency Intel 2 vCPU / 2 GB

[New Jersey, US](https://rackcensus.com/locations/new-jersey-vps-benchmarks "Every provider in New Jersey")

Benchmark complete

Finished Oct 15, 2026

Geekbench 7 single-core

1,508

Faster than 82% of 2 vCPU plans

Geekbench 7 multi-core

Skipped

Disk 4K IOPS

196,031

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

-

Provider

Vultr

-

Plan

High Frequency Intel 2 vCPU / 2 GB

-

Location

New Jersey, US

-

vCPU

2

-

RAM

2 GB

-

Storage

80 GB NVMe

-

Network

Unknown

-

OS image

2284

-

Trigger

Scheduled

-

Queued at

Oct 15, 2026, 22:29: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

- [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,508 | Skipped | [Geekbench Browser](https://browser.geekbench.com/v7/cpu/642011) |

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,44062nd of 192 | Single-core only |
| Navigation | 1,80214th of 192 | Single-core only |
| HTML5 Browser | 1,42152nd of 192 | Single-core only |
| PDF Viewer | 1,66234th of 192 | Single-core only |
| Photo Library | 1,23875th of 192 | Single-core only |
| Clang | 1,43334th of 192 | Single-core only |
| Text Processing | 1,42137th of 192 | Single-core only |
| Asset Compression | 1,71029th of 192 | Single-core only |
| HDR | 1,40359th of 192 | Single-core only |
| Photo Editor | 1,71044th of 192 | Single-core only |
| Ray Tracer | 1,46740th of 192 | Single-core only |
| Structure from Motion | 1,68347th of 192 | Single-core only |
| Game Physics | 1,31068th of 192 | Single-core only |
| Video Encoder | 1,43950th of 192 | Single-core only |
| Audio Encoder | 1,56644th of 192 | Single-core only |
| Video Player | 1,54754th of 192 | Single-core only |

Rank among the 192 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 | 33.2 GB/s | 3 | 0.775% |
| Scale higher is better | 21.2 GB/s | 3 | 0.797% |
| Add higher is better | 22.8 GB/s | 3 | 0.477% |
| Triad higher is better | 23 GB/s | 3 | 1.09% |

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 | 410/s | 3 | 0.591% |
| RSA 4096 verifies higher is better | 26,381/s | 3 | 0.386% |
| SHA-256 higher is better | 703 MB/s | 3 | 1.87% |
| AES-256-GCM higher is better | 9.68 GB/s | 3 | 1.12% |
| ChaCha20-Poly1305 higher is better | 5.2 GB/s | 3 | 1.19% |

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.91 ms | 3 | 0.728% |
| Requests per second, 90th percentile higher is better | 650/s | 3 | 0.178% |
| Request latency, 99.9th percentile lower is better | 6.61 ms | 3 | 1.94% |
| Requests per second, average higher is better | 631/s | 3 | 0.842% |

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

## Disk

| Block size | Read | Write | Total |
| --- | --- | --- | --- |
| 4K | 382.4 MB/s (97,886 IOPS) | 383.4 MB/s (98,145 IOPS) | 765.8 MB/s (196,031 IOPS) |
| 64K | 539.5 MB/s (8,632 IOPS) | 542.4 MB/s (8,677 IOPS) | 1.06 GB/s (17,309 IOPS) |
| 512K | 636.6 MB/s (1,273 IOPS) | 670.4 MB/s (1,340 IOPS) | 1.28 GB/s (2,613 IOPS) |
| 1M | 668.7 MB/s (668 IOPS) | 713.2 MB/s (713 IOPS) | 1.35 GB/s (1,381 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 | 824 Mbps | 875 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 872 Mbps | 1.75 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 722 Mbps | 599 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 877 Mbps | 1.42 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 941 Mbps | 1.88 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,893 | 0.072 ms |
| fdatasync | 12,899 | 0.078 ms |
| fsync | 10,712 | 0.093 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 11,726 | 0.085 ms |
| Two 8 kB writes |
| --- |
| open\_datasync | 7,011 | 0.143 ms |
| fdatasync | 11,885 | 0.084 ms |
| fsync | 9,329 | 0.107 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 5,546 | 0.18 ms |
| open\_sync at different write sizes |
| --- |
| 1 \* 16kB open\_sync write | 10,427 | 0.096 ms |
| 2 \* 8kB open\_sync writes | 5,590 | 0.179 ms |
| 4 \* 4kB open\_sync writes | 3,020 | 0.331 ms |
| 8 \* 2kB open\_sync writes | 1,295 | 0.772 ms |
| 16 \* 1kB open\_sync writes | 705 | 1.42 ms |
| fsync on a non-write descriptor |
| --- |
| write, fsync, close | 9,206 | 0.109 ms |
| write, close, fsync | 9,186 | 0.109 ms |
| Non-synced 8 kB writes |
| --- |
| write | 863,407 | 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,817 | 0.342 ms | 0.452 ms | 0.524 ms | 1.29 ms | 0 |
| Read/write (TPC-B like) | 8 | 5,278 | 1.43 ms | 2.38 ms | 3.15 ms | 5.02 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,950 | 5.26 ms | 14.5 ms | 24 ms | 38.1 ms | 0 |
| Read only | 1 | 28,498 | 0.032 ms | 0.047 ms | 0.057 ms | 0.079 ms | 0 |
| Read only | 8 | 49,494 | 0.149 ms | 0.243 ms | 0.294 ms | 0.436 ms | 0 |
| Read only | 32 | 52,075 | 0.54 ms | 0.931 ms | 1.23 ms | 1.95 ms | 0 |

Scale 10 (1,000,000 accounts), loaded in 1.18 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,918 | 0.514 ms | 0.719 ms | 0.955 ms | 2.47 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,721 | 1.64 ms | 2.44 ms | 3.38 ms | 5.27 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,064 | 6.04 ms | 9.4 ms | 11.6 ms | 15.6 ms | 0 |
| Read only | 1 | 8,644 | 0.062 ms | 0.257 ms | 0.385 ms | 0.966 ms | 0 |
| Read only | 8 | 33,381 | 0.201 ms | 0.481 ms | 0.636 ms | 1.95 ms | 0 |
| Read only | 32 | 33,930 | 0.81 ms | 1.61 ms | 2.28 ms | 4.05 ms | 0 |

Scale 100 (10,000,000 accounts), loaded in 12.9 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 | 510 | 10,205 | 1.82 ms | 2.62 ms | 4.33 ms | 0 |
| Read/write | 8 | 980 | 19,601 | 7.99 ms | 12.3 ms | 15.5 ms | 0 |
| Read/write | 32 | 1,004 | 20,082 | 30.8 ms | 53.9 ms | 69.3 ms | 1 |
| Read only | 1 | 1,110 | 17,761 | 0.856 ms | 1.16 ms | 1.39 ms | 0 |
| Read only | 8 | 1,899 | 30,389 | 4.1 ms | 5.67 ms | 6.79 ms | 0 |
| Read only | 32 | 1,752 | 28,031 | 18 ms | 22.7 ms | 25.7 ms | 0 |

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

### Redis

#### memtier

| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
| --- | --- | --- | --- | --- | --- |
| 1:10 set:get | 91,470 | 83,154 | 0.559 ms | 2.1 ms | 2.8 ms |
| 1:1 set:get | 88,598 | 44,299 | 0.567 ms | 2.19 ms | 2.85 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 | 600 | 2,076 | 3,291 | 686 ms |
| Express express-postgresjs | 6,418 | 10,664 | 30,886 | 85.9 ms |
| Fastify fastify-postgres | 6,095 | 10,937 | 35,196 | 76.4 ms |
| NestJS nestjs | 4,661 | 5,363 | 18,796 | 90.1 ms |
| Nuxt nuxt | 5,680 | 9,505 | 27,737 | 86.7 ms |
| FastAPI fastapi | 3,767 | 4,790 | 18,015 | 253 ms |
| Django django-postgresql | 1,898 | 2,136 | 5,181 | 203 ms |
| Rails rails | 2,852 | 4,459 | 16,169 | 115 ms |
| Laravel laravel | 786 | 830 | 1,637 | 347 ms |
| Symfony symfony | 1,015 | 1,103 | 3,139 | 279 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.3 | 691 ms | 826 ms | 900 ms | 0% |
| Shop page | 2.3 | 944 ms | 1.14 s | 1.19 s | 0% |
| Category page | 2.3 | 560 ms | 961 ms | 1.01 s | 0% |
| Product page | 2.3 | 627 ms | 753 ms | 812 ms | 0% |
| Product search | 2.3 | 555 ms | 658 ms | 731 ms | 0% |
| 32 virtual users |
| --- |
| Home page | 2.33 | 2.5 s | 2.81 s | 2.91 s | 0% |
| Shop page | 2.33 | 3.38 s | 3.81 s | 3.89 s | 0% |
| Category page | 2.33 | 2.97 s | 3.47 s | 3.76 s | 0% |
| Product page | 2.33 | 2.5 s | 2.73 s | 2.79 s | 0% |
| Product search | 2.33 | 2.3 s | 2.5 s | 2.56 s | 0% |

#### Cart and checkout

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 8 virtual users |
| --- |
| Add to cart | 4.49 | 736 ms | 896 ms | 1.03 s | 0% |
| Cart | 4.49 | 582 ms | 732 ms | 768 ms | 0% |
| Checkout | 4.49 | 444 ms | 563 ms | 601 ms | 0% |
| 32 virtual users |
| --- |
| Add to cart | 4.57 | 2.43 s | 2.97 s | 3.04 s | 0% |
| Cart | 4.57 | 2.52 s | 2.82 s | 2.91 s | 0% |
| Checkout | 4.57 | 1.95 s | 2.26 s | 2.31 s | 0% |

k6 with a fixed number of virtual users, 61 to 69 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.01 | 218 ms | 300 ms | 439 ms | 0% |
| Topic JSON | 1.02 | 113 ms | 146 ms | 292 ms | 0% |
| Home page | 1.02 | 191 ms | 304 ms | 398 ms | 0% |
| Categories page | 0.512 | 224 ms | 255 ms | 355 ms | 0% |
| User activity page | 0.512 | 140 ms | 190 ms | 227 ms | 0% |
| 4 virtual users |
| --- |
| Topic page | 3.51 | 504 ms | 665 ms | 1.02 s | 0% |
| Topic JSON | 1.76 | 279 ms | 372 ms | 459 ms | 0% |
| Home page | 1.75 | 455 ms | 595 ms | 822 ms | 0% |
| Categories page | 0.906 | 530 ms | 635 ms | 743 ms | 0% |
| User activity page | 0.874 | 313 ms | 393 ms | 576 ms | 0% |
| 16 virtual users |
| --- |
| Topic page | 3.23 | 1.67 s | 2.17 s | 2.41 s | 0% |
| Topic JSON | 1.68 | 1.39 s | 1.91 s | 2.02 s | 0% |
| Home page | 1.66 | 1.59 s | 2.04 s | 2.34 s | 0% |
| Categories page | 0.792 | 1.63 s | 2.21 s | 2.3 s | 0% |
| User activity page | 0.792 | 1.38 s | 1.89 s | 2.06 s | 0% |

#### Anonymous

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 16 virtual users |
| --- |
| Topic page | 70.3 | 63.8 ms | 152 ms | 209 ms | 0% |
| Topic JSON | 35.2 | 62.7 ms | 154 ms | 207 ms | 0% |
| Home page | 35.2 | 61.7 ms | 146 ms | 208 ms | 0% |
| Categories page | 17.6 | 66.8 ms | 158 ms | 215 ms | 0% |
| User activity page | 17.6 | 201 ms | 317 ms | 401 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 379 MB of it. The container peaked at 1,451 MB.

### Ghost

#### Readers

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 9.01 | 31.5 ms | 35.8 ms | 45.4 ms | 0% |
| Post page | 22.5 | 16.8 ms | 19.7 ms | 26.7 ms | 0% |
| Tag page | 4.5 | 21.6 ms | 25.2 ms | 35.5 ms | 0% |
| Author page | 4.5 | 21.2 ms | 24.6 ms | 35.4 ms | 0% |
| RSS feed | 4.5 | 26.6 ms | 30.9 ms | 33.3 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 10.5 | 99.3 ms | 130 ms | 146 ms | 0% |
| Post page | 26.3 | 69.7 ms | 99.1 ms | 127 ms | 0% |
| Tag page | 5.26 | 61.6 ms | 92.8 ms | 116 ms | 0% |
| Author page | 5.26 | 64.8 ms | 89.4 ms | 111 ms | 0% |
| RSS feed | 5.26 | 67.8 ms | 94.8 ms | 113 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 10.6 | 376 ms | 454 ms | 490 ms | 0% |
| Post page | 26.4 | 320 ms | 396 ms | 431 ms | 0% |
| Tag page | 5.26 | 206 ms | 272 ms | 296 ms | 0% |
| Author page | 5.3 | 207 ms | 271 ms | 314 ms | 0% |
| RSS feed | 5.26 | 215 ms | 290 ms | 312 ms | 0% |

#### Staff in Ghost Admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Post list | 4.84 | 30.8 ms | 39 ms | 56.4 ms | 0% |
| Post editor | 14.5 | 12.2 ms | 15.9 ms | 21.8 ms | 0% |
| Saving a draft | 14.5 | 29.8 ms | 39.1 ms | 54.5 ms | 0% |
| Member list | 4.84 | 37.4 ms | 45 ms | 59.5 ms | 0% |
| 4 virtual users |
| --- |
| Post list | 5.88 | 43.8 ms | 52.4 ms | 75.3 ms | 0% |
| Post editor | 17.7 | 22.9 ms | 29.6 ms | 44.7 ms | 0% |
| Saving a draft | 17.7 | 166 ms | 210 ms | 250 ms | 0% |
| Member list | 5.9 | 48.1 ms | 58.1 ms | 90.3 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 356 MB and MySQL at 581 MB.

### Wagtail

#### Visitors

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 1.76 | 75.6 ms | 83.8 ms | 89.8 ms | 0% |
| Blog index | 1.76 | 257 ms | 282 ms | 297 ms | 0% |
| Blog post | 5.28 | 24 ms | 36 ms | 39.8 ms | 0% |
| Bread page | 5.28 | 26 ms | 29.7 ms | 31.8 ms | 0% |
| Location page | 1.76 | 25 ms | 29.3 ms | 33.6 ms | 0% |
| Site search | 1.76 | 41.5 ms | 71.4 ms | 73 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 3.06 | 194 ms | 255 ms | 286 ms | 0% |
| Blog index | 3.11 | 600 ms | 835 ms | 891 ms | 0% |
| Blog post | 9.24 | 53.3 ms | 94.3 ms | 115 ms | 0% |
| Bread page | 9.28 | 59.4 ms | 83.7 ms | 96.4 ms | 0% |
| Location page | 3.11 | 56.9 ms | 81 ms | 87.4 ms | 0% |
| Site search | 3.08 | 76.7 ms | 171 ms | 213 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 3.12 | 592 ms | 811 ms | 998 ms | 0% |
| Blog index | 3.21 | 1.46 s | 1.67 s | 1.76 s | 0% |
| Blog post | 9.4 | 341 ms | 530 ms | 635 ms | 0% |
| Bread page | 9.47 | 345 ms | 538 ms | 618 ms | 0% |
| Location page | 3.17 | 340 ms | 546 ms | 718 ms | 0% |
| Site search | 3.16 | 407 ms | 644 ms | 720 ms | 0% |

#### Editors in the Wagtail admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Admin dashboard | 0.691 | 82.1 ms | 103 ms | 109 ms | 0% |
| Page explorer | 1.42 | 344 ms | 412 ms | 479 ms | 0% |
| Page editor | 2.11 | 156 ms | 188 ms | 255 ms | 0% |
| Image library | 0.691 | 59.6 ms | 64.9 ms | 491 ms | 0% |
| Admin page search | 0.691 | 32.1 ms | 73.7 ms | 77.8 ms | 0% |
| 4 virtual users |
| --- |
| Admin dashboard | 1.18 | 223 ms | 482 ms | 591 ms | 0% |
| Page explorer | 2.4 | 796 ms | 1.16 s | 1.27 s | 0% |
| Page editor | 3.6 | 363 ms | 655 ms | 758 ms | 0% |
| Image library | 1.2 | 206 ms | 443 ms | 528 ms | 0% |
| Admin page search | 1.18 | 81.5 ms | 261 ms | 487 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 299 MB, Postgres at 177 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:** 3792 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:** New Jersey, 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 15, 2026, 22:30:08 UTC

**Parser version:** 5

## Run timeline

**Queued:** Oct 15, 2026, 22:29:00 UTC

**First update from the server:** Oct 15, 2026, 22:29:53 UTC

**Completed:** Oct 15, 2026, 23:56:54 UTC

**Server deleted:** Oct 15, 2026, 23:56:54 UTC

**Cost of this run:** $0.037

Tests 59 of 59 done Live output 799 lines

Setup 2 cores, 1.9 GiB RAM 4 of 4Done

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

Network, IPv4 (iperf3) Median 872 Mbit/s send, 1.42 Gbit/s receive, 3 retried 5 of 5Done

Geekbench 7, single-core Score 1,508 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 00:56 UTC. It's read only now.

## Watch party

Loading the party