# Vultr Regular Performance Intel 2 vCPU / 2 GB

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

Benchmark complete

Finished Oct 14, 2026

Geekbench 7 single-core

656

Faster than 20% of 2 vCPU plans

Geekbench 7 multi-core

Skipped

Disk 4K IOPS

53,583

fio random read and write, 50/50

Monthly price at test time

$15.00

Same price today

## Server

[Vultr](https://rackcensus.com/vps-providers/vultr-benchmarks)[Regular Performance Intel 2 vCPU / 2 GB](https://rackcensus.com/plans/4d8kdt-vultr-regular-performance-intel-2-vcpu-2-gb-benchmarks?location=sea)

-

Provider

Vultr

-

Plan

Regular Performance Intel 2 vCPU / 2 GB

-

Location

Seattle, US

-

vCPU

2

-

RAM

2 GB

-

Storage

65 GB SSD

-

Network

Unknown

-

OS image

2284

-

Trigger

Scheduled

-

Queued at

Oct 14, 2026, 05:49: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

- [Chicago, US Oct 13, 2026](https://rackcensus.com/benchmarks/8l2pbt-vultr-regular-performance-intel-2-vcpu-2-gb-ord-benchmark)721
- [New Jersey, US Oct 10, 2026](https://rackcensus.com/benchmarks/hbb4oz-vultr-regular-performance-intel-2-vcpu-2-gb-ewr-benchmark)738

[Full history of this plan](https://rackcensus.com/plans/4d8kdt-vultr-regular-performance-intel-2-vcpu-2-gb-benchmarks/history)

## CPU

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

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 | 855129th of 151 | Single-core only |
| Navigation | 892133rd of 151 | Single-core only |
| HTML5 Browser | 527146th of 151 | Single-core only |
| PDF Viewer | 754132nd of 151 | Single-core only |
| Photo Library | 638128th of 151 | Single-core only |
| Clang | 660135th of 151 | Single-core only |
| Text Processing | 357150th of 151 | Single-core only |
| Asset Compression | 635139th of 151 | Single-core only |
| HDR | 725129th of 151 | Single-core only |
| Photo Editor | 803116th of 151 | Single-core only |
| Ray Tracer | 615139th of 151 | Single-core only |
| Structure from Motion | 696139th of 151 | Single-core only |
| Game Physics | 596140th of 151 | Single-core only |
| Video Encoder | 581138th of 151 | Single-core only |
| Audio Encoder | 800131st of 151 | Single-core only |
| Video Player | 584137th of 151 | Single-core only |

Rank among the 151 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 | 17.4 GB/s | 3 | 1.18% |
| Scale higher is better | 18.1 GB/s | 3 | 5.61% |
| Add higher is better | 20.3 GB/s | 3 | 2.42% |
| Triad higher is better | 19.7 GB/s | 3 | 3.4% |

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 | 232/s | 3 | 5% |
| RSA 4096 verifies higher is better | 15,005/s | 3 | 4.14% |
| SHA-256 higher is better | 361 MB/s | 3 | 4.04% |
| AES-256-GCM higher is better | 5.96 GB/s | 3 | 0.365% |
| ChaCha20-Poly1305 higher is better | 3.35 GB/s | 3 | 2.05% |

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.5 ms | 3 | 1.79% |
| Requests per second, 90th percentile higher is better | 406/s | 3 | 1.73% |
| Request latency, 99.9th percentile lower is better | 14.5 ms | 3 | 18% |
| Requests per second, average higher is better | 373/s | 3 | 2.28% |

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

## Disk

| Block size | Read | Write | Total |
| --- | --- | --- | --- |
| 4K | 104.5 MB/s (26,756 IOPS) | 104.8 MB/s (26,827 IOPS) | 209.3 MB/s (53,583 IOPS) |
| 64K | 181 MB/s (2,896 IOPS) | 182 MB/s (2,911 IOPS) | 363 MB/s (5,807 IOPS) |
| 512K | 208.5 MB/s (417 IOPS) | 219.6 MB/s (439 IOPS) | 428.1 MB/s (856 IOPS) |
| 1M | 224.8 MB/s (224 IOPS) | 239.8 MB/s (239 IOPS) | 464.7 MB/s (463 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.34 Gbps | 1.75 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 3.99 Gbps | 3.75 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 2.52 Gbps | 2.97 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 6.59 Gbps | 6.93 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 5.97 Gbps | 4.44 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 | 5,738 | 0.174 ms |
| fdatasync | 4,690 | 0.213 ms |
| fsync | 3,208 | 0.312 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 3,475 | 0.288 ms |
| Two 8 kB writes |
| --- |
| open\_datasync | 3,153 | 0.317 ms |
| fdatasync | 5,234 | 0.191 ms |
| fsync | 3,014 | 0.332 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 1,814 | 0.551 ms |
| open\_sync at different write sizes |
| --- |
| 1 \* 16kB open\_sync write | 3,196 | 0.313 ms |
| 2 \* 8kB open\_sync writes | 1,767 | 0.566 ms |
| 4 \* 4kB open\_sync writes | 1,002 | 0.998 ms |
| 8 \* 2kB open\_sync writes | 479 | 2.09 ms |
| 16 \* 1kB open\_sync writes | 253 | 3.95 ms |
| fsync on a non-write descriptor |
| --- |
| write, fsync, close | 3,031 | 0.33 ms |
| write, close, fsync | 2,839 | 0.352 ms |
| Non-synced 8 kB writes |
| --- |
| write | 504,960 | 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 | 1,313 | 0.72 ms | 0.966 ms | 1.35 ms | 3.85 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,758 | 2.67 ms | 4.78 ms | 6.73 ms | 13.4 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,504 | 10.3 ms | 28.6 ms | 46.9 ms | 77.5 ms | 0 |
| Read only | 1 | 15,798 | 0.057 ms | 0.095 ms | 0.136 ms | 0.295 ms | 0 |
| Read only | 8 | 28,853 | 0.251 ms | 0.438 ms | 0.565 ms | 1.47 ms | 0 |
| Read only | 32 | 26,463 | 1.03 ms | 1.93 ms | 2.64 ms | 4.78 ms | 0 |

Scale 10 (1,000,000 accounts), loaded in 3 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 | 953 | 0.993 ms | 1.43 ms | 2.75 ms | 5.87 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,453 | 2.97 ms | 5.68 ms | 9.46 ms | 24 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,405 | 12.2 ms | 22.4 ms | 29.6 ms | 50.2 ms | 0 |
| Read only | 1 | 3,563 | 0.287 ms | 0.488 ms | 1.61 ms | 3.79 ms | 0 |
| Read only | 8 | 17,300 | 0.364 ms | 0.962 ms | 2.02 ms | 4.27 ms | 0 |
| Read only | 32 | 17,194 | 1.57 ms | 3.35 ms | 5.04 ms | 9.24 ms | 0 |

Scale 100 (10,000,000 accounts), loaded in 31.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.

### MySQL

#### sysbench OLTP

| Workload | Threads | Transactions/s | Queries/s | Median | p95 | p99 | Errors |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Read/write | 1 | 200 | 4,009 | 4.41 ms | 7.7 ms | 19.6 ms | 0 |
| Read/write | 8 | 506 | 10,127 | 15.3 ms | 25.3 ms | 35 ms | 0 |
| Read/write | 32 | 468 | 9,354 | 65.6 ms | 115 ms | 142 ms | 0 |
| Read only | 1 | 487 | 7,797 | 1.96 ms | 2.76 ms | 3.43 ms | 0 |
| Read only | 8 | 898 | 14,374 | 8.74 ms | 12.8 ms | 15.3 ms | 0 |
| Read only | 32 | 759 | 12,152 | 41.1 ms | 55.8 ms | 64.5 ms | 0 |

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

### Redis

#### memtier

| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
| --- | --- | --- | --- | --- | --- |
| 1:10 set:get | 44,325 | 40,295 | 1.15 ms | 3.78 ms | 6.21 ms |
| 1:1 set:get | 43,504 | 21,752 | 1.2 ms | 3.84 ms | 6.34 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 | 283 | 1,023 | 1,672 | 1.99 s |
| Express express-postgresjs | 5,018 | 6,354 | 16,721 | 339 ms |
| Fastify fastify-postgres | 4,586 | 6,857 | 19,159 | 189 ms |
| NestJS nestjs | 2,266 | 2,943 | 10,388 | 196 ms |
| Nuxt nuxt | 3,957 | 6,172 | 17,245 | 280 ms |
| FastAPI fastapi | 1,736 | 2,442 | 8,482 | 571 ms |
| Django django-postgresql | 752 | 911 | 2,223 | 515 ms |
| Rails rails | 1,398 | 2,080 | 7,358 | 311 ms |
| Laravel laravel | 349 | 356 | 647 | 884 ms |
| Symfony symfony | 415 | 449 | 1,468 | 668 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 | 0.785 | 1.99 s | 2.15 s | 2.21 s | 0% |
| Shop page | 0.785 | 2.65 s | 2.85 s | 2.94 s | 0% |
| Category page | 0.785 | 1.65 s | 2.72 s | 2.84 s | 0% |
| Product page | 0.785 | 1.8 s | 2.05 s | 2.12 s | 0% |
| Product search | 0.785 | 1.58 s | 1.88 s | 1.96 s | 0% |
| 32 virtual users |
| --- |
| Home page | 0.897 | 6.96 s | 7.7 s | 7.89 s | 0% |
| Shop page | 0.897 | 9.47 s | 11.3 s | 11.7 s | 0% |
| Category page | 0.897 | 8.4 s | 11 s | 11.3 s | 0% |
| Product page | 0.701 | 7.06 s | 7.69 s | 7.85 s | 0% |
| Product search | 0.448 | 6.9 s | 7.18 s | 7.25 s | 0% |

#### Cart and checkout

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 8 virtual users |
| --- |
| Add to cart | 1.42 | 2.13 s | 2.31 s | 2.44 s | 0% |
| Cart | 1.42 | 1.7 s | 1.89 s | 1.91 s | 0% |
| Checkout | 1.42 | 1.35 s | 1.48 s | 1.52 s | 0% |
| 32 virtual users |
| --- |
| Add to cart | 1.64 | 6.66 s | 8.3 s | 8.42 s | 0% |
| Cart | 1.55 | 7.36 s | 8 s | 8.12 s | 0% |
| Checkout | 1.34 | 5.75 s | 6.64 s | 6.73 s | 0% |

k6 with a fixed number of virtual users, 66 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 | 0.781 | 557 ms | 647 ms | 864 ms | 0% |
| Topic JSON | 0.391 | 300 ms | 357 ms | 359 ms | 0% |
| Home page | 0.407 | 501 ms | 782 ms | 1.11 s | 0% |
| Categories page | 0.195 | 585 ms | 712 ms | 805 ms | 0% |
| User activity page | 0.195 | 336 ms | 369 ms | 386 ms | 0% |
| 4 virtual users |
| --- |
| Topic page | 1.31 | 1.28 s | 2.03 s | 3.07 s | 0% |
| Topic JSON | 0.665 | 720 ms | 878 ms | 1.12 s | 0% |
| Home page | 0.649 | 1.17 s | 1.72 s | 2.01 s | 0% |
| Categories page | 0.324 | 1.37 s | 1.6 s | 1.74 s | 0% |
| User activity page | 0.324 | 765 ms | 1.02 s | 1.36 s | 0% |
| 16 virtual users |
| --- |
| Topic page | 1.23 | 2.52 s | 3.28 s | 4.23 s | 0% |
| Topic JSON | 0.617 | 1.84 s | 2.2 s | 2.28 s | 0% |
| Home page | 0.633 | 2.4 s | 2.97 s | 3.2 s | 0% |
| Categories page | 0.317 | 2.6 s | 3.02 s | 3.1 s | 0% |
| User activity page | 0.301 | 1.95 s | 2.86 s | 3.37 s | 0% |

#### Anonymous

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 16 virtual users |
| --- |
| Topic page | 25.6 | 166 ms | 420 ms | 530 ms | 0.193% |
| Topic JSON | 12.9 | 155 ms | 413 ms | 546 ms | 0.256% |
| Home page | 12.8 | 170 ms | 411 ms | 553 ms | 0.128% |
| Categories page | 6.45 | 155 ms | 420 ms | 564 ms | 0.255% |
| User activity page | 6.4 | 577 ms | 942 ms | 1.12 s | 0.257% |

k6 with a fixed number of virtual users, 61 to 63 s per level, after a 23 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 348 MB of it. The container peaked at 1,412 MB.

### Ghost

#### Readers

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 3.76 | 78.8 ms | 94.6 ms | 112 ms | 0% |
| Post page | 9.4 | 39.7 ms | 50.6 ms | 69.4 ms | 0% |
| Tag page | 1.88 | 50.3 ms | 62 ms | 73.5 ms | 0% |
| Author page | 1.88 | 51 ms | 63 ms | 80 ms | 0% |
| RSS feed | 1.88 | 58.6 ms | 71.4 ms | 77.2 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 4.47 | 246 ms | 349 ms | 402 ms | 0% |
| Post page | 11.1 | 157 ms | 231 ms | 317 ms | 0% |
| Tag page | 2.24 | 142 ms | 231 ms | 305 ms | 0% |
| Author page | 2.21 | 151 ms | 203 ms | 270 ms | 0% |
| RSS feed | 2.19 | 169 ms | 227 ms | 256 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 4.45 | 927 ms | 1.12 s | 1.29 s | 0% |
| Post page | 11.1 | 755 ms | 944 ms | 1.09 s | 0% |
| Tag page | 2.21 | 500 ms | 666 ms | 762 ms | 0% |
| Author page | 2.21 | 499 ms | 649 ms | 713 ms | 0% |
| RSS feed | 2.18 | 497 ms | 663 ms | 719 ms | 0% |

#### Staff in Ghost Admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Post list | 2.17 | 67.2 ms | 89.7 ms | 100 ms | 0% |
| Post editor | 6.51 | 27 ms | 37 ms | 50.7 ms | 0% |
| Saving a draft | 6.51 | 66.4 ms | 84.8 ms | 134 ms | 0% |
| Member list | 2.17 | 85.4 ms | 106 ms | 192 ms | 0% |
| 4 virtual users |
| --- |
| Post list | 2.7 | 96.3 ms | 129 ms | 207 ms | 0% |
| Post editor | 8.11 | 49.1 ms | 66 ms | 99.3 ms | 0% |
| Saving a draft | 8.14 | 353 ms | 479 ms | 574 ms | 0% |
| Member list | 2.7 | 104 ms | 132 ms | 173 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. 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 340 MB and MySQL at 579 MB.

### Wagtail

#### Visitors

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 0.681 | 194 ms | 237 ms | 287 ms | 0% |
| Blog index | 0.681 | 670 ms | 771 ms | 876 ms | 0% |
| Blog post | 2.03 | 61.3 ms | 98.2 ms | 123 ms | 0% |
| Bread page | 2.04 | 67 ms | 83 ms | 99 ms | 0% |
| Location page | 0.681 | 64.4 ms | 82.6 ms | 101 ms | 0% |
| Site search | 0.681 | 94.5 ms | 167 ms | 189 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 1.19 | 447 ms | 667 ms | 816 ms | 0% |
| Blog index | 1.23 | 1.62 s | 2.29 s | 2.38 s | 0% |
| Blog post | 3.6 | 131 ms | 227 ms | 277 ms | 0% |
| Bread page | 3.63 | 139 ms | 211 ms | 266 ms | 0% |
| Location page | 1.23 | 135 ms | 228 ms | 299 ms | 0% |
| Site search | 1.19 | 204 ms | 427 ms | 554 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 1.32 | 1.37 s | 1.72 s | 1.89 s | 0% |
| Blog index | 1.43 | 3.38 s | 3.91 s | 4.24 s | 0% |
| Blog post | 4 | 748 ms | 1.2 s | 1.42 s | 0% |
| Bread page | 4.05 | 785 ms | 1.34 s | 1.87 s | 0% |
| Location page | 1.39 | 792 ms | 1.27 s | 1.38 s | 0% |
| Site search | 1.32 | 961 ms | 1.48 s | 1.66 s | 0% |

#### Editors in the Wagtail admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Admin dashboard | 0.276 | 201 ms | 293 ms | 464 ms | 0% |
| Page explorer | 0.584 | 795 ms | 1.05 s | 1.1 s | 0% |
| Page editor | 0.875 | 357 ms | 455 ms | 668 ms | 0% |
| Image library | 0.292 | 131 ms | 370 ms | 1.31 s | 0% |
| Admin page search | 0.276 | 112 ms | 193 ms | 200 ms | 0% |
| 4 virtual users |
| --- |
| Admin dashboard | 0.512 | 525 ms | 957 ms | 1.02 s | 0% |
| Page explorer | 1.04 | 1.75 s | 2.69 s | 3.23 s | 0% |
| Page editor | 1.57 | 781 ms | 1.39 s | 1.55 s | 0% |
| Image library | 0.528 | 450 ms | 860 ms | 1.05 s | 0% |
| Admin page search | 0.512 | 240 ms | 606 ms | 684 ms | 0% |

k6 with a fixed number of virtual users, 60 to 63 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 294 MB, Postgres at 175 MB, and Redis at 26 MB.

## Advertised vs. measured

| Spec | Advertised | Measured |
| --- | --- | --- |
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0.4% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 65 GB SSD | 60.9 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 Xeon Processor (Skylake, IBRS)

**CPU cores:** 2

**CPU frequency:** 2594 MHz

**AES-NI:** Yes

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

**RAM reported:** 1.9 GiB

**Swap reported:** 6.2 GiB

**Disk reported:** 60.9 GiB

**Virtualization reported:** MICROSOFT

**CPU steal:** 0.4% 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:** Regular Performance Intel 2 vCPU / 2 GB

**Product line:** Cloud Compute Regular

**Location:** Seattle, US

**vCPU:** 2 shared vCPU

**Architecture:** x86\_64

**RAM:** 2 GB

**Storage:** 65 GB SSD

**Virtualization:** KVM

**Network:** Unknown

**Transfer:** 3.07 TB

**Port 25:** On request

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

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

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

**Ran at:** Oct 14, 2026, 05:51:42 UTC

**Parser version:** 5

## Run timeline

**Queued:** Oct 14, 2026, 05:49:00 UTC

**First update from the server:** Oct 14, 2026, 05:50:09 UTC

**Completed:** Oct 14, 2026, 07:43:55 UTC

**Server deleted:** Oct 14, 2026, 07:43:55 UTC

**Cost of this run:** $0.040

Tests 59 of 59 done Live output 797 lines

Setup 2 cores, 1.9 GiB RAM 4 of 4Done

Disk (fio) 219 MB/s at 4k, 487 MB/s at 1m 5 of 5Done

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

Geekbench 7, single-core Score 656 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 08:43 UTC. It's read only now.

## Watch party

Loading the party