OVHcloud D2-2
Beauharnois
Server
-
ProviderOVHcloud
-
PlanD2-2
-
LocationBeauharnois
-
vCPU1
-
RAM2 GB
-
Storage25 GB NVMe
-
Network100 Mbps
-
OS imageUbuntu 24.04
-
TriggerScheduled
-
Queued atOct 13, 2026, 22:24:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 663 | Skipped | Geekbench Browser |
Multi-core was skipped because Geekbench 7 needs about 2.1 GB of free memory to run 1 thread, 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 |
610
|
Single-core only |
| Navigation |
864
|
Single-core only |
| HTML5 Browser |
639
|
Single-core only |
| PDF Viewer |
718
|
Single-core only |
| Photo Library |
514
|
Single-core only |
| Clang |
596
|
Single-core only |
| Text Processing |
659
|
Single-core only |
| Asset Compression |
706
|
Single-core only |
| HDR |
681
|
Single-core only |
| Photo Editor |
750
|
Single-core only |
| Ray Tracer |
721
|
Single-core only |
| Structure from Motion |
807
|
Single-core only |
| Game Physics |
578
|
Single-core only |
| Video Encoder |
602
|
Single-core only |
| Audio Encoder |
649
|
Single-core only |
| Video Player |
606
|
Single-core only |
Rank among the 150 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.5 GB/s | 3 | 1.52% |
| Scale higher is better | 10.1 GB/s | 3 | 2.15% |
| Add higher is better | 11.2 GB/s | 3 | 3.12% |
| Triad higher is better | 11.2 GB/s | 3 | 2.39% |
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 | 89.2/s | 3 | 4.38% |
| RSA 4096 verifies higher is better | 5,903/s | 3 | 3.1% |
| SHA-256 higher is better | 161 MB/s | 3 | 1.98% |
| AES-256-GCM higher is better | 1.53 GB/s | 3 | 3.78% |
| ChaCha20-Poly1305 higher is better | 1.2 GB/s | 3 | 0.769% |
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 | 5.82 ms | 3 | 1.24% |
| Requests per second, 90th percentile higher is better | 168/s | 3 | 1.24% |
| Request latency, 99.9th percentile lower is better | 15.4 ms | 3 | 8.83% |
| Requests per second, average higher is better | 160/s | 3 | 1.04% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 35.5 MB/s (9,088 IOPS) | 35.6 MB/s (9,113 IOPS) | 71.1 MB/s (18,201 IOPS) |
| 64K | 640.1 MB/s (10,241 IOPS) | 643.5 MB/s (10,295 IOPS) | 1.25 GB/s (20,536 IOPS) |
| 512K | 908.9 MB/s (1,817 IOPS) | 957.2 MB/s (1,914 IOPS) | 1.82 GB/s (3,731 IOPS) |
| 1M | 845.6 MB/s (845 IOPS) | 901.9 MB/s (901 IOPS) | 1.71 GB/s (1,746 IOPS) |
fio random read and write, 50/50, run by YABS against the boot disk.
Network
IPv4 transfer speed
| Target | Protocol | Send | Receive |
|---|---|---|---|
| Clouvider, London, UK (10G) | IPv4 | 94.7 Mbps | 96 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 94.6 Mbps | 93.4 Mbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 85.9 Mbps | 77.9 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 85.8 Mbps | 96.1 Mbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 97.4 Mbps | 97.5 Mbps |
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 | 4,765 | 0.21 ms |
| fdatasync | 4,635 | 0.216 ms |
| fsync | 2,859 | 0.35 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 2,908 | 0.344 ms |
| Two 8 kB writes | ||
| open_datasync | 2,442 | 0.41 ms |
| fdatasync | 4,563 | 0.219 ms |
| fsync | 2,711 | 0.369 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,578 | 0.634 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 3,122 | 0.32 ms |
| 2 * 8kB open_sync writes | 1,542 | 0.648 ms |
| 4 * 4kB open_sync writes | 411 | 2.43 ms |
| 8 * 2kB open_sync writes | 524 | 1.91 ms |
| 16 * 1kB open_sync writes | 235 | 4.25 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 2,524 | 0.396 ms |
| write, close, fsync | 2,515 | 0.398 ms |
| Non-synced 8 kB writes | ||
| write | 570,251 | 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,180 | 0.789 ms | 1.14 ms | 1.88 ms | 3.15 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,230 | 5.67 ms | 9.64 ms | 13 ms | 24.9 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,165 | 23.1 ms | 59.9 ms | 91.8 ms | 145 ms | 0 |
| Read only | 1 | 12,594 | 0.069 ms | 0.125 ms | 0.174 ms | 0.965 ms | 0 |
| Read only | 8 | 12,952 | 0.56 ms | 1.03 ms | 1.36 ms | 2.33 ms | 0 |
| Read only | 32 | 10,842 | 2.51 ms | 4.15 ms | 5.95 ms | 8.95 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 2.83 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 | 787 | 1.17 ms | 1.86 ms | 3.86 ms | 6.39 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,084 | 6.86 ms | 11.2 ms | 15.6 ms | 31.2 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,078 | 28.3 ms | 41.6 ms | 52.4 ms | 73.7 ms | 0 |
| Read only | 1 | 2,127 | 0.407 ms | 0.806 ms | 1.63 ms | 2.99 ms | 0 |
| Read only | 8 | 5,622 | 1.28 ms | 2.76 ms | 4.07 ms | 9.26 ms | 0 |
| Read only | 32 | 5,867 | 4.64 ms | 8.98 ms | 11.6 ms | 16.4 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 29.8 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 | 176 | 3,513 | 5.09 ms | 9.39 ms | 14.7 ms | 0 |
| Read/write | 8 | 210 | 4,208 | 36.2 ms | 54.8 ms | 68.1 ms | 0 |
| Read/write | 32 | 227 | 4,538 | 135 ms | 212 ms | 253 ms | 0 |
| Read only | 1 | 435 | 6,963 | 2.15 ms | 3.19 ms | 4.49 ms | 0 |
| Read only | 8 | 413 | 6,613 | 18.6 ms | 26.2 ms | 31.9 ms | 0 |
| Read only | 32 | 372 | 5,959 | 84.5 ms | 111 ms | 130 ms | 0 |
10 tables of 100,000 rows, loaded in 29 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 23,344 | 21,221 | 2.53 ms | 6.24 ms | 10.9 ms |
| 1:1 set:get | 22,742 | 11,370 | 2.56 ms | 6.66 ms | 11.5 ms |
1,000,000 keys of 32 bytes. 64 connections over 1 thread, 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 | 123 | 464 | 581 | 7.4 s |
| Express express-postgresjs | 2,234 | 2,775 | 5,912 | 4.67 s |
| Fastify fastify-postgres | 2,320 | 3,096 | 5,566 | 4.47 s |
| NestJS nestjs | 1,044 | 1,207 | 3,759 | 853 ms |
| Nuxt nuxt | 1,813 | 2,723 | 4,504 | 5.69 s |
| FastAPI fastapi | 915 | 1,082 | 3,864 | 1.13 s |
| Django django-postgresql | 415 | 459 | 1,070 | 740 ms |
| Rails rails | 778 | 1,071 | 3,522 | 413 ms |
| Laravel laravel | 181 | 208 | 354 | 1.62 s |
| Symfony symfony | 233 | 249 | 751 | 1.24 s |
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.489 | 2.93 s | 4.04 s | 4.08 s | 0% |
| Shop page | 0.489 | 4.05 s | 5.01 s | 5.1 s | 0% |
| Category page | 0.489 | 2.9 s | 4.19 s | 4.81 s | 0% |
| Product page | 0.489 | 2.76 s | 4.11 s | 4.49 s | 0% |
| Product search | 0.489 | 2.59 s | 3.17 s | 3.4 s | 0% |
| 32 virtual users | |||||
| Home page | 0.675 | 9.07 s | 12.5 s | 12.6 s | 0% |
| Shop page | 0.45 | 13.5 s | 15.2 s | 15.6 s | 0% |
| Category page | 0.45 | 13.7 s | 15.6 s | 15.9 s | 0% |
| Product page | 0.45 | 11.8 s | 12.4 s | 12.5 s | 0% |
| Product search | 0.45 | 11.8 s | 12.1 s | 12.2 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 0.894 | 2.82 s | 3.43 s | 3.53 s | 0% |
| Cart | 0.894 | 2.73 s | 3.1 s | 3.24 s | 0% |
| Checkout | 0.894 | 2.17 s | 2.48 s | 2.68 s | 0% |
| 32 virtual users | |||||
| Add to cart | 1.18 | 9.22 s | 12.6 s | 13.2 s | 0% |
| Cart | 0.9 | 11.7 s | 13 s | 13.2 s | 0% |
| Checkout | 0.9 | 8.38 s | 9.84 s | 10.1 s | 0% |
k6 with a fixed number of virtual users, 65 to 72 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.681 | 610 ms | 851 ms | 891 ms | 0% |
| Topic JSON | 0.357 | 318 ms | 466 ms | 535 ms | 0% |
| Home page | 0.357 | 573 ms | 945 ms | 1.1 s | 0% |
| Categories page | 0.178 | 645 ms | 835 ms | 863 ms | 0% |
| User activity page | 0.162 | 365 ms | 524 ms | 540 ms | 0% |
| 4 virtual users | |||||
| Topic page | 0.687 | 2.33 s | 2.76 s | 3.75 s | 0% |
| Topic JSON | 0.352 | 1.24 s | 1.49 s | 1.74 s | 0% |
| Home page | 0.352 | 2.11 s | 2.38 s | 2.43 s | 0% |
| Categories page | 0.192 | 2.57 s | 3.86 s | 3.91 s | 0% |
| User activity page | 0.176 | 1.34 s | 1.55 s | 1.56 s | 0% |
| 16 virtual users | |||||
| Topic page | 0.66 | 3.3 s | 4.27 s | 5.3 s | 0% |
| Topic JSON | 0.314 | 2.49 s | 3.35 s | 3.93 s | 0% |
| Home page | 0.314 | 3.02 s | 4.49 s | 5.27 s | 0% |
| Categories page | 0.173 | 3.29 s | 3.63 s | 3.74 s | 0% |
| User activity page | 0.173 | 2.58 s | 3.46 s | 3.79 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 14.5 | 292 ms | 717 ms | 989 ms | 1.58% |
| Topic JSON | 7.23 | 278 ms | 676 ms | 919 ms | 1.58% |
| Home page | 7.23 | 283 ms | 652 ms | 1.01 s | 1.58% |
| Categories page | 3.65 | 313 ms | 933 ms | 2.45 s | 0.897% |
| User activity page | 3.63 | 906 ms | 1.79 s | 2.16 s | 2.25% |
k6 with a fixed number of virtual users, 61 to 64 s per level, after a 24 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 added a 2 GB swapfile first, the way its installer does, and used up to 503 MB of it. The container peaked at 1,484 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 2.89 | 95.3 ms | 134 ms | 159 ms | 0% |
| Post page | 7.22 | 49 ms | 82.4 ms | 133 ms | 0% |
| Tag page | 1.45 | 64.2 ms | 91 ms | 196 ms | 0% |
| Author page | 1.45 | 66.7 ms | 95.4 ms | 153 ms | 0% |
| RSS feed | 1.45 | 69.8 ms | 98.7 ms | 227 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.74 | 382 ms | 573 ms | 650 ms | 0% |
| Post page | 6.87 | 253 ms | 426 ms | 566 ms | 0% |
| Tag page | 1.38 | 231 ms | 358 ms | 426 ms | 0% |
| Author page | 1.36 | 246 ms | 350 ms | 403 ms | 0% |
| RSS feed | 1.35 | 249 ms | 437 ms | 508 ms | 0% |
| 16 virtual users | |||||
| Home page | 3.23 | 1.25 s | 1.53 s | 1.66 s | 0% |
| Post page | 8.05 | 1.02 s | 1.34 s | 1.43 s | 0% |
| Tag page | 1.63 | 687 ms | 880 ms | 977 ms | 0% |
| Author page | 1.6 | 678 ms | 933 ms | 1.01 s | 0% |
| RSS feed | 1.6 | 672 ms | 917 ms | 980 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 1.49 | 100 ms | 160 ms | 178 ms | 0% |
| Post editor | 4.5 | 37.7 ms | 74.6 ms | 130 ms | 0% |
| Saving a draft | 4.5 | 87.3 ms | 132 ms | 217 ms | 0% |
| Member list | 1.49 | 127 ms | 193 ms | 359 ms | 0% |
| 4 virtual users | |||||
| Post list | 1.79 | 124 ms | 173 ms | 221 ms | 0% |
| Post editor | 5.39 | 71.7 ms | 108 ms | 221 ms | 0% |
| Saving a draft | 5.41 | 526 ms | 775 ms | 938 ms | 0% |
| Member list | 1.79 | 160 ms | 235 ms | 322 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 331 MB and MySQL at 576 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 0.897 | 149 ms | 188 ms | 201 ms | 0% |
| Blog index | 0.897 | 510 ms | 593 ms | 712 ms | 0% |
| Blog post | 2.66 | 46.1 ms | 68.6 ms | 93.9 ms | 0% |
| Bread page | 2.67 | 49.9 ms | 67.9 ms | 81.4 ms | 0% |
| Location page | 0.897 | 46.9 ms | 64.9 ms | 82.5 ms | 0% |
| Site search | 0.88 | 80.2 ms | 149 ms | 160 ms | 0% |
| 4 virtual users | |||||
| Home page | 0.731 | 752 ms | 923 ms | 965 ms | 0% |
| Blog index | 0.78 | 2.48 s | 3.02 s | 3.15 s | 0% |
| Blog post | 2.19 | 207 ms | 332 ms | 430 ms | 0% |
| Bread page | 2.24 | 230 ms | 308 ms | 335 ms | 0% |
| Location page | 0.78 | 216 ms | 290 ms | 372 ms | 0% |
| Site search | 0.715 | 424 ms | 681 ms | 703 ms | 0% |
| 16 virtual users | |||||
| Home page | 0.696 | 2.62 s | 3.35 s | 3.71 s | 0% |
| Blog index | 0.745 | 6.56 s | 7.38 s | 7.85 s | 0% |
| Blog post | 2.07 | 1.47 s | 2.47 s | 2.67 s | 0% |
| Bread page | 2.12 | 1.53 s | 2.28 s | 2.78 s | 0% |
| Location page | 0.712 | 1.44 s | 2.5 s | 2.79 s | 0% |
| Site search | 0.712 | 1.74 s | 2.84 s | 3.1 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.342 | 160 ms | 189 ms | 201 ms | 0% |
| Page explorer | 0.699 | 676 ms | 729 ms | 819 ms | 0% |
| Page editor | 1.04 | 308 ms | 427 ms | 614 ms | 0% |
| Image library | 0.342 | 111 ms | 331 ms | 1.36 s | 0% |
| Admin page search | 0.342 | 64.2 ms | 155 ms | 328 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.257 | 915 ms | 1.2 s | 1.23 s | 0% |
| Page explorer | 0.579 | 3.61 s | 4.41 s | 4.48 s | 0% |
| Page editor | 0.852 | 1.44 s | 2.1 s | 2.17 s | 0% |
| Image library | 0.257 | 449 ms | 1.08 s | 1.15 s | 0% |
| Admin page search | 0.257 | 302 ms | 547 ms | 616 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 290 MB, Postgres at 175 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 1 | 1 |
| CPU | Shared vCPU | 0.5% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 25 GB NVMe | 24.1 GiB |
| Architecture | x86_64 | x86_64 |
| Virtualization | KVM | KVM |
Guests usually report slightly less RAM and disk than advertised because of kernel reservations and filesystem overhead.
Detected hardware
- CPU model
- Intel Core Processor (Haswell, no TSX)
- CPU cores
- 1
- CPU frequency
- 2400 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- Yes
- RAM reported
- 1.9 GiB
- Swap reported
- 0 MiB
- Disk reported
- 24.1 GiB
- Virtualization reported
- KVM
- CPU steal
- 0.5% of busy CPU time stolen
- Distro
- Ubuntu 24.04.4 LTS
- Kernel
- 6.8.0-136-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- Yes
Advertised at test time
- Plan
- D2-2
- Product line
- Discovery D2
- Location
- Beauharnois
- vCPU
- 1 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 25 GB NVMe
- Virtualization
- KVM
- Network
- 100 Mbps
- Transfer
- Unmetered
- Port 25
- Unknown
- Monthly price at test time
- $6.74
- Hourly price at test time
- $0.012
- YABS version
- v2026-09-20
- Ran at
- Oct 13, 2026, 22:26:56 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 13, 2026, 22:24:00 UTC
- First update from the server
- Oct 13, 2026, 22:25:12 UTC
- Completed
- Oct 14, 2026, 00:15:00 UTC
- Server deleted
- Oct 14, 2026, 00:15:00 UTC
- Cost of this run
- $0.023
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading output.
This party closed at . It's read only now.
Reconnecting. Hang tight.