# Vultr Regular Performance Intel 2 vCPU / 2 GB

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

Benchmark complete

Finished Oct 13, 2026

Geekbench 7 single-core

721

Faster than 14% of 2 vCPU plans

Geekbench 7 multi-core

Skipped

Disk 4K IOPS

44,331

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

-

Provider

Vultr

-

Plan

Regular Performance Intel 2 vCPU / 2 GB

-

Location

Chicago, US

-

vCPU

2

-

RAM

2 GB

-

Storage

65 GB SSD

-

Network

Unknown

-

OS image

2284

-

Trigger

Scheduled

-

Queued at

Oct 13, 2026, 03:04: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 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 | 721 | Skipped | [Geekbench Browser](https://browser.geekbench.com/v7/cpu/618649) |

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 | 931107th of 129 | Single-core only |
| Navigation | 922116th of 129 | Single-core only |
| HTML5 Browser | 543126th of 129 | Single-core only |
| PDF Viewer | 843116th of 129 | Single-core only |
| Photo Library | 693107th of 129 | Single-core only |
| Clang | 739115th of 129 | Single-core only |
| Text Processing | 359129th of 129 | Single-core only |
| Asset Compression | 722116th of 129 | Single-core only |
| HDR | 806102nd of 129 | Single-core only |
| Photo Editor | 91296th of 129 | Single-core only |
| Ray Tracer | 629122nd of 129 | Single-core only |
| Structure from Motion | 794120th of 129 | Single-core only |
| Game Physics | 733116th of 129 | Single-core only |
| Video Encoder | 676117th of 129 | Single-core only |
| Audio Encoder | 921107th of 129 | Single-core only |
| Video Player | 613119th of 129 | Single-core only |

Rank among the 129 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 | 21.3 GB/s | 3 | 12.5% |
| Scale higher is better | 16.1 GB/s | 3 | 20.2% |
| Add higher is better | 18.9 GB/s | 3 | 20.6% |
| Triad higher is better | 18.6 GB/s | 3 | 21% |

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 | 283/s | 3 | 3.14% |
| RSA 4096 verifies higher is better | 17,675/s | 3 | 6.78% |
| SHA-256 higher is better | 427 MB/s | 3 | 1.12% |
| AES-256-GCM higher is better | 5.98 GB/s | 3 | 13.6% |
| ChaCha20-Poly1305 higher is better | 3.94 GB/s | 3 | 1.31% |

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.14 ms | 3 | 0.67% |
| Requests per second, 90th percentile higher is better | 457/s | 3 | 0.456% |
| Request latency, 99.9th percentile lower is better | 10.1 ms | 3 | 0.656% |
| Requests per second, average higher is better | 432/s | 3 | 0.98% |

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

## Disk

| Block size | Read | Write | Total |
| --- | --- | --- | --- |
| 4K | 86.5 MB/s (22,136 IOPS) | 86.7 MB/s (22,195 IOPS) | 173.2 MB/s (44,331 IOPS) |
| 64K | 129.2 MB/s (2,067 IOPS) | 129.9 MB/s (2,078 IOPS) | 259.1 MB/s (4,145 IOPS) |
| 512K | 150.5 MB/s (300 IOPS) | 158.5 MB/s (316 IOPS) | 309 MB/s (616 IOPS) |
| 1M | 164.4 MB/s (164 IOPS) | 175.3 MB/s (175 IOPS) | 339.7 MB/s (339 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.01 Gbps | 2.46 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 7.57 Gbps | 4.09 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 2.55 Gbps | 3.48 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 3.55 Gbps | 4.18 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 7.34 Gbps | 4.42 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 | 7,378 | 0.136 ms |
| fdatasync | 7,138 | 0.14 ms |
| fsync | 4,961 | 0.202 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 5,324 | 0.188 ms |
| Two 8 kB writes |
| --- |
| open\_datasync | 3,566 | 0.28 ms |
| fdatasync | 5,770 | 0.173 ms |
| fsync | 4,309 | 0.232 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 2,848 | 0.351 ms |
| open\_sync at different write sizes |
| --- |
| 1 \* 16kB open\_sync write | 4,914 | 0.204 ms |
| 2 \* 8kB open\_sync writes | 2,634 | 0.38 ms |
| 4 \* 4kB open\_sync writes | 1,497 | 0.668 ms |
| 8 \* 2kB open\_sync writes | 819 | 1.22 ms |
| 16 \* 1kB open\_sync writes | 405 | 2.47 ms |
| fsync on a non-write descriptor |
| --- |
| write, fsync, close | 3,567 | 0.28 ms |
| write, close, fsync | 4,541 | 0.22 ms |
| Non-synced 8 kB writes |
| --- |
| write | 596,199 | 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,777 | 0.532 ms | 0.686 ms | 0.891 ms | 2.62 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,320 | 2.21 ms | 3.85 ms | 5.59 ms | 14.9 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,058 | 8.46 ms | 23.1 ms | 38.9 ms | 73.4 ms | 0 |
| Read only | 1 | 19,258 | 0.048 ms | 0.068 ms | 0.083 ms | 0.143 ms | 0 |
| Read only | 8 | 32,276 | 0.224 ms | 0.378 ms | 0.489 ms | 1.62 ms | 0 |
| Read only | 32 | 29,814 | 0.937 ms | 1.56 ms | 2.15 ms | 4.01 ms | 0 |

Scale 10 (1,000,000 accounts), loaded in 3.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,088 | 0.826 ms | 1.47 ms | 3.01 ms | 7.57 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,640 | 2.63 ms | 5.39 ms | 11 ms | 24.2 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,215 | 9.94 ms | 18.3 ms | 102 ms | 801 ms | 0 |
| Read only | 1 | 3,788 | 0.255 ms | 0.458 ms | 1.94 ms | 4.51 ms | 0 |
| Read only | 8 | 17,152 | 0.318 ms | 0.874 ms | 2.5 ms | 23.3 ms | 0 |
| Read only | 32 | 20,009 | 1.26 ms | 2.7 ms | 4.9 ms | 30.6 ms | 0 |

Scale 100 (10,000,000 accounts), loaded in 38 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 | 202 | 4,041 | 3.43 ms | 9.39 ms | 37.6 ms | 0 |
| Read/write | 8 | 501 | 10,020 | 14.7 ms | 31.4 ms | 50.1 ms | 0 |
| Read/write | 32 | 568 | 11,369 | 52.9 ms | 97.6 ms | 128 ms | 0 |
| Read only | 1 | 610 | 9,762 | 1.55 ms | 2.07 ms | 2.57 ms | 0 |
| Read only | 8 | 1,113 | 17,806 | 7.04 ms | 9.73 ms | 11.4 ms | 0 |
| Read only | 32 | 987 | 15,788 | 31.9 ms | 41.9 ms | 47.5 ms | 0 |

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

### Redis

#### memtier

| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
| --- | --- | --- | --- | --- | --- |
| 1:10 set:get | 51,717 | 47,015 | 0.863 ms | 3.47 ms | 5.66 ms |
| 1:1 set:get | 51,689 | 25,844 | 0.991 ms | 3.26 ms | 5.6 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 | 264 | 1,210 | 1,730 | 3.25 s |
| Express express-postgresjs | 5,371 | 7,079 | 22,329 | 90 ms |
| Fastify fastify-postgres | 4,917 | 8,328 | 26,905 | 108 ms |
| NestJS nestjs | 2,915 | 3,427 | 12,103 | 166 ms |
| Nuxt nuxt | 4,308 | 6,532 | 20,954 | 332 ms |
| FastAPI fastapi | 1,963 | 2,846 | 8,691 | 556 ms |
| Django django-postgresql | 921 | 1,112 | 2,717 | 462 ms |
| Rails rails | 1,606 | 2,220 | 8,122 | 213 ms |
| Laravel laravel | 412 | 463 | 816 | 682 ms |
| Symfony symfony | 450 | 518 | 1,578 | 679 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.921 | 1.69 s | 1.81 s | 1.94 s | 0% |
| Shop page | 0.921 | 2.24 s | 2.51 s | 2.57 s | 0% |
| Category page | 0.921 | 1.4 s | 2.34 s | 2.48 s | 0% |
| Product page | 0.921 | 1.55 s | 1.74 s | 1.81 s | 0% |
| Product search | 0.921 | 1.36 s | 1.57 s | 1.63 s | 0% |
| 32 virtual users |
| --- |
| Home page | 0.934 | 5.77 s | 6.5 s | 6.6 s | 0% |
| Shop page | 0.934 | 7.69 s | 8.76 s | 8.85 s | 0% |
| Category page | 0.934 | 6.9 s | 8.46 s | 8.68 s | 0% |
| Product page | 0.934 | 6.4 s | 7.07 s | 7.14 s | 0% |
| Product search | 0.934 | 6.46 s | 7.23 s | 7.29 s | 0% |

#### Cart and checkout

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 8 virtual users |
| --- |
| Add to cart | 1.84 | 1.72 s | 1.95 s | 2.03 s | 0% |
| Cart | 1.84 | 1.4 s | 1.56 s | 1.6 s | 0% |
| Checkout | 1.84 | 1.1 s | 1.32 s | 1.38 s | 0% |
| 32 virtual users |
| --- |
| Add to cart | 1.82 | 5.71 s | 7.22 s | 7.4 s | 0% |
| Cart | 1.82 | 6.22 s | 7.02 s | 7.18 s | 0% |
| Checkout | 1.82 | 4.96 s | 5.81 s | 5.91 s | 0% |

k6 with a fixed number of virtual users, 63 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 | 0.95 | 455 ms | 554 ms | 908 ms | 0% |
| Topic JSON | 0.491 | 229 ms | 275 ms | 291 ms | 0% |
| Home page | 0.491 | 411 ms | 473 ms | 521 ms | 0% |
| Categories page | 0.246 | 479 ms | 716 ms | 826 ms | 0% |
| User activity page | 0.246 | 287 ms | 329 ms | 359 ms | 0% |
| 4 virtual users |
| --- |
| Topic page | 1.47 | 1.14 s | 1.46 s | 1.91 s | 0% |
| Topic JSON | 0.745 | 613 ms | 751 ms | 882 ms | 0% |
| Home page | 0.728 | 1.04 s | 1.37 s | 2.25 s | 0% |
| Categories page | 0.388 | 1.3 s | 1.85 s | 2.41 s | 0% |
| User activity page | 0.372 | 724 ms | 973 ms | 1.71 s | 0% |
| 16 virtual users |
| --- |
| Topic page | 1.36 | 2.29 s | 3.03 s | 3.48 s | 0% |
| Topic JSON | 0.654 | 1.75 s | 2.11 s | 2.79 s | 0% |
| Home page | 0.686 | 2.23 s | 2.62 s | 2.74 s | 0% |
| Categories page | 0.335 | 2.42 s | 2.7 s | 2.78 s | 0% |
| User activity page | 0.351 | 1.78 s | 2.19 s | 2.48 s | 0% |

#### Anonymous

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 16 virtual users |
| --- |
| Topic page | 29.5 | 143 ms | 377 ms | 565 ms | 0.0559% |
| Topic JSON | 14.9 | 131 ms | 358 ms | 530 ms | 0% |
| Home page | 14.8 | 150 ms | 389 ms | 697 ms | 0% |
| Categories page | 7.42 | 127 ms | 321 ms | 902 ms | 0.222% |
| User activity page | 7.4 | 489 ms | 900 ms | 1.12 s | 0% |

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 393 MB of it. The container peaked at 1,474 MB.

### Ghost

#### Readers

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 4.53 | 66 ms | 76.5 ms | 92.6 ms | 0% |
| Post page | 11.3 | 32.5 ms | 41.4 ms | 58.9 ms | 0% |
| Tag page | 2.26 | 42.9 ms | 52.6 ms | 93.7 ms | 0% |
| Author page | 2.26 | 43.9 ms | 50.8 ms | 77.3 ms | 0% |
| RSS feed | 2.26 | 49.6 ms | 58 ms | 63.8 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 5.48 | 201 ms | 256 ms | 304 ms | 0% |
| Post page | 13.7 | 127 ms | 190 ms | 256 ms | 0% |
| Tag page | 2.74 | 120 ms | 174 ms | 243 ms | 0% |
| Author page | 2.73 | 131 ms | 199 ms | 260 ms | 0% |
| RSS feed | 2.73 | 133 ms | 199 ms | 267 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 5.3 | 763 ms | 981 ms | 1.26 s | 0% |
| Post page | 13.3 | 616 ms | 803 ms | 1.19 s | 0% |
| Tag page | 2.68 | 414 ms | 587 ms | 657 ms | 0% |
| Author page | 2.64 | 423 ms | 584 ms | 669 ms | 0% |
| RSS feed | 2.66 | 415 ms | 566 ms | 589 ms | 0% |

#### Staff in Ghost Admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Post list | 2.6 | 58.4 ms | 83.1 ms | 135 ms | 0% |
| Post editor | 7.86 | 21.7 ms | 30.7 ms | 36.9 ms | 0% |
| Saving a draft | 7.86 | 53.2 ms | 72.7 ms | 95.9 ms | 0% |
| Member list | 2.62 | 71 ms | 92.9 ms | 147 ms | 0% |
| 4 virtual users |
| --- |
| Post list | 3.14 | 74.9 ms | 97.1 ms | 118 ms | 0% |
| Post editor | 9.49 | 41.7 ms | 57.4 ms | 118 ms | 0% |
| Saving a draft | 9.51 | 302 ms | 401 ms | 469 ms | 0% |
| Member list | 3.17 | 93.3 ms | 117 ms | 194 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 342 MB and MySQL at 580 MB.

### Wagtail

#### Visitors

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 0.881 | 158 ms | 174 ms | 175 ms | 0% |
| Blog index | 0.881 | 493 ms | 555 ms | 568 ms | 0% |
| Blog post | 2.63 | 49 ms | 74.1 ms | 79.2 ms | 0% |
| Bread page | 2.63 | 54.1 ms | 61.1 ms | 65.7 ms | 0% |
| Location page | 0.881 | 52.9 ms | 59.5 ms | 60 ms | 0% |
| Site search | 0.881 | 91.8 ms | 147 ms | 158 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 1.38 | 424 ms | 688 ms | 1.08 s | 0% |
| Blog index | 1.43 | 1.27 s | 1.77 s | 2.14 s | 0% |
| Blog post | 4.16 | 120 ms | 223 ms | 283 ms | 0% |
| Bread page | 4.19 | 129 ms | 186 ms | 349 ms | 0% |
| Location page | 1.43 | 120 ms | 175 ms | 251 ms | 0% |
| Site search | 1.38 | 177 ms | 332 ms | 606 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 1.46 | 1.28 s | 1.6 s | 1.76 s | 0% |
| Blog index | 1.49 | 3.12 s | 3.95 s | 4.24 s | 0% |
| Blog post | 4.39 | 725 ms | 1.11 s | 1.32 s | 0% |
| Bread page | 4.41 | 754 ms | 1.08 s | 1.29 s | 0% |
| Location page | 1.48 | 707 ms | 1.02 s | 1.33 s | 0% |
| Site search | 1.46 | 912 ms | 1.24 s | 1.36 s | 0% |

#### Editors in the Wagtail admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Admin dashboard | 0.308 | 181 ms | 213 ms | 215 ms | 0% |
| Page explorer | 0.648 | 725 ms | 815 ms | 1.03 s | 0% |
| Page editor | 0.939 | 335 ms | 440 ms | 689 ms | 0% |
| Image library | 0.308 | 120 ms | 267 ms | 1.19 s | 0% |
| Admin page search | 0.308 | 72.7 ms | 149 ms | 155 ms | 0% |
| 4 virtual users |
| --- |
| Admin dashboard | 0.517 | 516 ms | 807 ms | 843 ms | 0% |
| Page explorer | 1.08 | 1.63 s | 2.59 s | 3.14 s | 0% |
| Page editor | 1.61 | 922 ms | 1.36 s | 1.49 s | 0% |
| Image library | 0.549 | 415 ms | 833 ms | 970 ms | 0% |
| Admin page search | 0.517 | 164 ms | 320 ms | 598 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. 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 291 MB, Postgres at 176 MB, and Redis at 26 MB.

## Advertised vs. measured

| Spec | Advertised | Measured |
| --- | --- | --- |
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0.9% 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.9% 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:** Chicago, 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 13, 2026, 03:06:42 UTC

**Parser version:** 5

## Run timeline

**Queued:** Oct 13, 2026, 03:04:00 UTC

**First update from the server:** Oct 13, 2026, 03:05:18 UTC

**Completed:** Oct 13, 2026, 04:43:02 UTC

**Server deleted:** Oct 13, 2026, 04:43:02 UTC

**Cost of this run:** $0.035

Tests 59 of 59 done Live output 797 lines

Setup 2 cores, 1.9 GiB RAM 4 of 4Done

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

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

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

## Watch party

Loading the party