# Vultr Regular Performance 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 17, 2026

Geekbench 7 single-core

717

Faster than 12% of 2 vCPU plans

Median here: 728 over 2 runs in 90 days

Geekbench 7 multi-core

Skipped

Disk 4K IOPS

49,351

fio random read and write, 50/50

Median here: 52,687 over 2 runs in 90 days

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

-

Provider

Vultr

-

Plan

Regular Performance Intel 2 vCPU / 2 GB

-

Location

New Jersey, US

-

vCPU

2

-

RAM

2 GB

-

Storage

65 GB SSD

-

Network

Unknown

-

OS image

2284

-

Trigger

Scheduled

-

Queued at

Oct 17, 2026, 02: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

- [Miami, US Oct 15, 2026](https://rackcensus.com/benchmarks/h2e2fx-vultr-regular-performance-intel-2-vcpu-2-gb-mia-benchmark)706
- [Seattle, US Oct 14, 2026](https://rackcensus.com/benchmarks/exvhwe-vultr-regular-performance-intel-2-vcpu-2-gb-sea-benchmark)656
- [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 | 717 | Skipped | [Geekbench Browser](https://browser.geekbench.com/v7/cpu/650630) |

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 | 930174th of 217 | Single-core only |
| Navigation | 962179th of 217 | Single-core only |
| HTML5 Browser | 540208th of 217 | Single-core only |
| PDF Viewer | 833185th of 217 | Single-core only |
| Photo Library | 679179th of 217 | Single-core only |
| Clang | 735186th of 217 | Single-core only |
| Text Processing | 342215th of 217 | Single-core only |
| Asset Compression | 689192nd of 217 | Single-core only |
| HDR | 768176th of 217 | Single-core only |
| Photo Editor | 961150th of 217 | Single-core only |
| Ray Tracer | 638196th of 217 | Single-core only |
| Structure from Motion | 879176th of 217 | Single-core only |
| Game Physics | 743183rd of 217 | Single-core only |
| Video Encoder | 589196th of 217 | Single-core only |
| Audio Encoder | 847181st of 217 | Single-core only |
| Video Player | 666186th 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 | 23.9 GB/s | 3 | 14.1% |
| Scale higher is better | 19 GB/s | 3 | 2.45% |
| Add higher is better | 22.2 GB/s | 3 | 1.53% |
| Triad higher is better | 21.5 GB/s | 3 | 1.94% |

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 | 278/s | 3 | 0.784% |
| RSA 4096 verifies higher is better | 18,014/s | 3 | 0.499% |
| SHA-256 higher is better | 407 MB/s | 3 | 2.05% |
| AES-256-GCM higher is better | 6.56 GB/s | 3 | 0.981% |
| ChaCha20-Poly1305 higher is better | 3.84 GB/s | 3 | 2.76% |

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.22 ms | 3 | 0.38% |
| Requests per second, 90th percentile higher is better | 435/s | 3 | 1.28% |
| Request latency, 99.9th percentile lower is better | 10.8 ms | 3 | 1.07% |
| Requests per second, average higher is better | 420/s | 3 | 1.12% |

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

## Disk

| Block size | Read | Write | Total |
| --- | --- | --- | --- |
| 4K | 96.3 MB/s (24,643 IOPS) | 96.5 MB/s (24,708 IOPS) | 192.8 MB/s (49,351 IOPS) |
| 64K | 159.2 MB/s (2,547 IOPS) | 160.1 MB/s (2,561 IOPS) | 319.3 MB/s (5,108 IOPS) |
| 512K | 183.4 MB/s (366 IOPS) | 193.2 MB/s (386 IOPS) | 376.6 MB/s (752 IOPS) |
| 1M | 180 MB/s (180 IOPS) | 192 MB/s (191 IOPS) | 372 MB/s (371 IOPS) |

fio random read and write, 50/50, run by YABS against the boot disk.

## Network

iperf3 didn't report network results for this run.

## Datastores

### PostgreSQL

#### fsync speed (pg\_test\_fsync)

| Method | Operations per second | Time per operation |
| --- | --- | --- |
| One 8 kB write |
| --- |
| open\_datasync | 6,693 | 0.149 ms |
| fdatasync | 6,160 | 0.162 ms |
| fsync | 4,475 | 0.223 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 4,966 | 0.201 ms |
| Two 8 kB writes |
| --- |
| open\_datasync | 3,596 | 0.278 ms |
| fdatasync | 6,043 | 0.165 ms |
| fsync | 4,053 | 0.247 ms |
| fsync\_writethrough | Not supported here | n/a |
| open\_sync | 2,471 | 0.405 ms |
| open\_sync at different write sizes |
| --- |
| 1 \* 16kB open\_sync write | 4,403 | 0.227 ms |
| 2 \* 8kB open\_sync writes | 2,574 | 0.389 ms |
| 4 \* 4kB open\_sync writes | 1,422 | 0.703 ms |
| 8 \* 2kB open\_sync writes | 647 | 1.55 ms |
| 16 \* 1kB open\_sync writes | 343 | 2.92 ms |
| fsync on a non-write descriptor |
| --- |
| write, fsync, close | 4,190 | 0.239 ms |
| write, close, fsync | 4,188 | 0.239 ms |
| Non-synced 8 kB writes |
| --- |
| write | 592,586 | 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,711 | 0.551 ms | 0.741 ms | 0.975 ms | 2.63 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,345 | 2.2 ms | 3.85 ms | 5.52 ms | 13.1 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,066 | 8.52 ms | 23.4 ms | 38.7 ms | 78.4 ms | 0 |
| Read only | 1 | 19,378 | 0.048 ms | 0.068 ms | 0.083 ms | 0.133 ms | 0 |
| Read only | 8 | 32,037 | 0.227 ms | 0.381 ms | 0.477 ms | 1.13 ms | 0 |
| Read only | 32 | 31,641 | 0.89 ms | 1.44 ms | 1.95 ms | 3.75 ms | 0 |

Scale 10 (1,000,000 accounts), loaded in 3.21 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 | 986 | 0.927 ms | 1.45 ms | 2.83 ms | 7.18 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,641 | 2.62 ms | 5.54 ms | 11 ms | 25.4 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,447 | 12.3 ms | 20.5 ms | 27.3 ms | 46.6 ms | 0 |
| Read only | 1 | 3,627 | 0.273 ms | 0.499 ms | 1.87 ms | 4.16 ms | 0 |
| Read only | 8 | 18,271 | 0.334 ms | 0.882 ms | 2.11 ms | 4.78 ms | 0 |
| Read only | 32 | 21,526 | 1.26 ms | 2.6 ms | 3.78 ms | 6.72 ms | 0 |

Scale 100 (10,000,000 accounts), loaded in 34.6 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 | 247 | 4,932 | 3.43 ms | 5.37 ms | 22.3 ms | 0 |
| Read/write | 8 | 562 | 11,246 | 13.2 ms | 25.7 ms | 41.9 ms | 0 |
| Read/write | 32 | 567 | 11,340 | 53.9 ms | 95.8 ms | 126 ms | 0 |
| Read only | 1 | 595 | 9,519 | 1.58 ms | 2.15 ms | 2.62 ms | 0 |
| Read only | 8 | 1,087 | 17,392 | 7.17 ms | 10.3 ms | 12.1 ms | 0 |
| Read only | 32 | 1,012 | 16,193 | 30.8 ms | 40.4 ms | 45.8 ms | 0 |

10 tables of 100,000 rows, loaded in 14.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 | 50,774 | 46,158 | 0.959 ms | 3.6 ms | 8.32 ms |
| 1:1 set:get | 51,433 | 25,716 | 1.02 ms | 3.33 ms | 5.86 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 | 306 | 1,271 | 1,948 | 1.69 s |
| Express express-postgresjs | 5,485 | 7,480 | 21,665 | 271 ms |
| Fastify fastify-postgres | 5,016 | 8,203 | 26,565 | 376 ms |
| NestJS nestjs | 3,067 | 3,516 | 12,512 | 158 ms |
| Nuxt nuxt | 4,363 | 7,098 | 20,473 | 481 ms |
| FastAPI fastapi | 2,016 | 2,895 | 9,279 | 503 ms |
| Django django-postgresql | 959 | 1,130 | 2,881 | 441 ms |
| Rails rails | 1,723 | 2,561 | 8,923 | 195 ms |
| Laravel laravel | 415 | 413 | 860 | 681 ms |
| Symfony symfony | 491 | 558 | 1,752 | 845 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 | 0.991 | 1.55 s | 1.74 s | 1.81 s | 0% |
| Shop page | 0.991 | 2.14 s | 2.29 s | 2.34 s | 0% |
| Category page | 0.991 | 1.39 s | 2.15 s | 2.18 s | 0% |
| Product page | 0.991 | 1.42 s | 1.61 s | 1.66 s | 0% |
| Product search | 0.991 | 1.25 s | 1.46 s | 1.55 s | 0% |
| 32 virtual users |
| --- |
| Home page | 0.932 | 6.19 s | 6.9 s | 6.97 s | 0% |
| Shop page | 0.932 | 8.1 s | 9.31 s | 9.39 s | 0% |
| Category page | 0.932 | 7.3 s | 8.65 s | 8.86 s | 0% |
| Product page | 0.932 | 6.2 s | 6.52 s | 6.57 s | 0% |
| Product search | 0.932 | 5.91 s | 6.34 s | 6.47 s | 0% |

#### Cart and checkout

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 8 virtual users |
| --- |
| Add to cart | 1.92 | 1.71 s | 1.9 s | 1.94 s | 0% |
| Cart | 1.92 | 1.34 s | 1.5 s | 1.55 s | 0% |
| Checkout | 1.92 | 1.09 s | 1.21 s | 1.25 s | 0% |
| 32 virtual users |
| --- |
| Add to cart | 1.88 | 5.63 s | 7.8 s | 8.13 s | 0% |
| Cart | 1.88 | 5.93 s | 7.47 s | 7.8 s | 0% |
| Checkout | 1.88 | 4.77 s | 5.46 s | 5.68 s | 0% |

k6 with a fixed number of virtual users, 63 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 | 0.946 | 454 ms | 667 ms | 1.06 s | 0% |
| Topic JSON | 0.473 | 224 ms | 289 ms | 316 ms | 0% |
| Home page | 0.473 | 417 ms | 620 ms | 696 ms | 0% |
| Categories page | 0.245 | 475 ms | 496 ms | 497 ms | 0% |
| User activity page | 0.228 | 268 ms | 571 ms | 687 ms | 0% |
| 4 virtual users |
| --- |
| Topic page | 1.56 | 1.11 s | 1.32 s | 2.23 s | 0% |
| Topic JSON | 0.779 | 613 ms | 701 ms | 733 ms | 0% |
| Home page | 0.779 | 1.03 s | 1.22 s | 1.48 s | 0% |
| Categories page | 0.39 | 1.18 s | 2.78 s | 3.02 s | 0% |
| User activity page | 0.39 | 649 ms | 1.2 s | 1.45 s | 0% |
| 16 virtual users |
| --- |
| Topic page | 1.66 | 2.11 s | 2.77 s | 2.99 s | 0% |
| Topic JSON | 0.803 | 1.61 s | 2.42 s | 2.56 s | 0% |
| Home page | 0.82 | 2.05 s | 2.93 s | 3.36 s | 0% |
| Categories page | 0.402 | 2.1 s | 2.68 s | 3.27 s | 0% |
| User activity page | 0.434 | 1.7 s | 2.27 s | 2.47 s | 0% |

#### Anonymous

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 16 virtual users |
| --- |
| Topic page | 38.6 | 118 ms | 259 ms | 360 ms | 0.0428% |
| Topic JSON | 19.4 | 118 ms | 272 ms | 419 ms | 0% |
| Home page | 19.4 | 119 ms | 276 ms | 416 ms | 0% |
| Categories page | 9.69 | 120 ms | 287 ms | 505 ms | 0% |
| User activity page | 9.69 | 350 ms | 538 ms | 859 ms | 0% |

k6 with a fixed number of virtual users, 60 to 62 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 416 MB of it. The container peaked at 1,502 MB.

### Ghost

#### Readers

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 4.65 | 60.5 ms | 77.1 ms | 133 ms | 0% |
| Post page | 11.6 | 32 ms | 42.4 ms | 60.9 ms | 0% |
| Tag page | 2.33 | 42.2 ms | 57.5 ms | 74.2 ms | 0% |
| Author page | 2.31 | 40.4 ms | 52.1 ms | 58.4 ms | 0% |
| RSS feed | 2.31 | 50.6 ms | 62.2 ms | 75.9 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 5.55 | 190 ms | 245 ms | 312 ms | 0% |
| Post page | 13.9 | 128 ms | 189 ms | 243 ms | 0% |
| Tag page | 2.78 | 122 ms | 198 ms | 276 ms | 0% |
| Author page | 2.79 | 124 ms | 181 ms | 238 ms | 0% |
| RSS feed | 2.74 | 134 ms | 179 ms | 215 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 5.54 | 738 ms | 924 ms | 960 ms | 0% |
| Post page | 13.8 | 593 ms | 761 ms | 825 ms | 0% |
| Tag page | 2.76 | 393 ms | 573 ms | 624 ms | 0% |
| Author page | 2.78 | 409 ms | 529 ms | 603 ms | 0% |
| RSS feed | 2.75 | 403 ms | 565 ms | 613 ms | 0% |

#### Staff in Ghost Admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Post list | 2.7 | 57.4 ms | 75.6 ms | 107 ms | 0% |
| Post editor | 8.14 | 21 ms | 28.7 ms | 38.9 ms | 0% |
| Saving a draft | 8.14 | 51.5 ms | 66.4 ms | 105 ms | 0% |
| Member list | 2.72 | 68.8 ms | 83.9 ms | 101 ms | 0% |
| 4 virtual users |
| --- |
| Post list | 3.22 | 80.7 ms | 100 ms | 162 ms | 0% |
| Post editor | 9.7 | 40 ms | 55.8 ms | 99.1 ms | 0% |
| Saving a draft | 9.73 | 298 ms | 402 ms | 478 ms | 0% |
| Member list | 3.23 | 89.4 ms | 112 ms | 203 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 346 MB and MySQL at 580 MB.

### Wagtail

#### Visitors

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Home page | 0.847 | 161 ms | 180 ms | 191 ms | 0% |
| Blog index | 0.847 | 538 ms | 608 ms | 634 ms | 0% |
| Blog post | 2.54 | 50.6 ms | 78.9 ms | 82 ms | 0% |
| Bread page | 2.54 | 55.9 ms | 63.4 ms | 66.7 ms | 0% |
| Location page | 0.847 | 52.5 ms | 61.7 ms | 64.9 ms | 0% |
| Site search | 0.847 | 86.3 ms | 154 ms | 158 ms | 0% |
| 4 virtual users |
| --- |
| Home page | 1.5 | 391 ms | 559 ms | 581 ms | 0% |
| Blog index | 1.55 | 1.25 s | 1.65 s | 1.79 s | 0% |
| Blog post | 4.49 | 104 ms | 199 ms | 231 ms | 0% |
| Bread page | 4.54 | 120 ms | 172 ms | 202 ms | 0% |
| Location page | 1.55 | 115 ms | 169 ms | 182 ms | 0% |
| Site search | 1.48 | 184 ms | 333 ms | 374 ms | 0% |
| 16 virtual users |
| --- |
| Home page | 1.6 | 1.2 s | 1.51 s | 1.76 s | 0% |
| Blog index | 1.65 | 2.88 s | 3.26 s | 3.56 s | 0% |
| Blog post | 4.77 | 678 ms | 963 ms | 1.13 s | 0% |
| Bread page | 4.81 | 684 ms | 1.03 s | 1.23 s | 0% |
| Location page | 1.62 | 673 ms | 955 ms | 1.06 s | 0% |
| Site search | 1.57 | 790 ms | 1.23 s | 1.34 s | 0% |

#### Editors in the Wagtail admin

| Step | Requests/s | Median | p95 | p99 | Error rate |
| --- | --- | --- | --- | --- | --- |
| 1 virtual user |
| --- |
| Admin dashboard | 0.323 | 167 ms | 229 ms | 231 ms | 0% |
| Page explorer | 0.663 | 708 ms | 783 ms | 886 ms | 0% |
| Page editor | 0.97 | 322 ms | 520 ms | 680 ms | 0% |
| Image library | 0.323 | 120 ms | 196 ms | 1.17 s | 0% |
| Admin page search | 0.323 | 72.4 ms | 139 ms | 141 ms | 0% |
| 4 virtual users |
| --- |
| Admin dashboard | 0.552 | 597 ms | 1.06 s | 1.16 s | 0% |
| Page explorer | 1.14 | 1.66 s | 2.69 s | 2.94 s | 0% |
| Page editor | 1.67 | 786 ms | 1.31 s | 1.55 s | 0% |
| Image library | 0.552 | 393 ms | 756 ms | 781 ms | 0% |
| Admin page search | 0.552 | 157 ms | 371 ms | 473 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 294 MB, Postgres at 175 MB, and Redis at 26 MB.

## Advertised vs. measured

| Spec | Advertised | Measured |
| --- | --- | --- |
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0.3% 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.3% 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:** New Jersey, 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 17, 2026, 02:31:50 UTC

**Parser version:** 5

## Run timeline

**Queued:** Oct 17, 2026, 02:29:00 UTC

**First update from the server:** Oct 17, 2026, 02:30:12 UTC

**Completed:** Oct 17, 2026, 04:05:44 UTC

**Server deleted:** Oct 17, 2026, 04:05:44 UTC

**Cost of this run:** $0.034

Tests 54 of 54 done Live output 771 lines

Setup 2 cores, 1.9 GiB RAM 4 of 4Done

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

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

## Watch party

Loading the party