Scaleway DEV1-S
Server
-
ProviderScaleway
-
PlanDEV1-S
-
LocationParis 2
-
vCPU2
-
RAM2 GB
-
Storage20 GB SSD
-
Network200 Mbps
-
OS imageubuntu_noble
-
TriggerScheduled
-
Queued atOct 15, 2026, 00:01:00 UTC
Latest runs of this plan
Full history of this planCPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 899 | Skipped | Geekbench Browser |
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,078
|
Single-core only |
| Navigation |
954
|
Single-core only |
| HTML5 Browser |
815
|
Single-core only |
| PDF Viewer |
1,037
|
Single-core only |
| Photo Library |
905
|
Single-core only |
| Clang |
747
|
Single-core only |
| Text Processing |
721
|
Single-core only |
| Asset Compression |
913
|
Single-core only |
| HDR |
822
|
Single-core only |
| Photo Editor |
1,034
|
Single-core only |
| Ray Tracer |
807
|
Single-core only |
| Structure from Motion |
1,122
|
Single-core only |
| Game Physics |
780
|
Single-core only |
| Video Encoder |
852
|
Single-core only |
| Audio Encoder |
1,017
|
Single-core only |
| Video Player |
906
|
Single-core only |
Rank among the 170 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 | 29.7 GB/s | 3 | 1.3% |
| Scale higher is better | 23.1 GB/s | 3 | 3.29% |
| Add higher is better | 24.6 GB/s | 3 | 0.987% |
| Triad higher is better | 24.1 GB/s | 3 | 0.297% |
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 | 369/s | 3 | 2.93% |
| RSA 4096 verifies higher is better | 23,778/s | 3 | 1.48% |
| SHA-256 higher is better | 1.14 GB/s | 3 | 2% |
| AES-256-GCM higher is better | 5.4 GB/s | 3 | 4.06% |
| ChaCha20-Poly1305 higher is better | 3.12 GB/s | 3 | 1.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 | 5.29 ms | 3 | 0.303% |
| Requests per second, 90th percentile higher is better | 371/s | 3 | 1.27% |
| Request latency, 99.9th percentile lower is better | 11.2 ms | 3 | 5.74% |
| Requests per second, average higher is better | 356/s | 3 | 1.62% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 124.3 MB/s (31,827 IOPS) | 124.7 MB/s (31,911 IOPS) | 249 MB/s (63,738 IOPS) |
| 64K | 825 MB/s (13,199 IOPS) | 829.3 MB/s (13,268 IOPS) | 1.62 GB/s (26,467 IOPS) |
| 512K | 1.51 GB/s (3,090 IOPS) | 1.59 GB/s (3,254 IOPS) | 3.1 GB/s (6,344 IOPS) |
| 1M | 1.58 GB/s (1,617 IOPS) | 1.69 GB/s (1,725 IOPS) | 3.27 GB/s (3,342 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 | busy | 5.93 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 457 Mbps | 6.78 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 436 Mbps | 1.41 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 435 Mbps | 1.47 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 450 Mbps | 3.27 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 | 494 | 2.03 ms |
| fdatasync | 487 | 2.05 ms |
| fsync | 225 | 4.44 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 228 | 4.38 ms |
| Two 8 kB writes | ||
| open_datasync | 263 | 3.8 ms |
| fdatasync | 445 | 2.25 ms |
| fsync | 192 | 5.21 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 107 | 9.37 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 214 | 4.68 ms |
| 2 * 8kB open_sync writes | 117 | 8.57 ms |
| 4 * 4kB open_sync writes | 57.5 | 17.4 ms |
| 8 * 2kB open_sync writes | 30.4 | 32.9 ms |
| 16 * 1kB open_sync writes | 14.9 | 67 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 224 | 4.47 ms |
| write, close, fsync | 234 | 4.27 ms |
| Non-synced 8 kB writes | ||
| write | 872,472 | 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 | 301 | 2.72 ms | 6.4 ms | 9.72 ms | 23.4 ms | 0 |
| Read/write (TPC-B like) | 8 | 979 | 6.57 ms | 17.7 ms | 27.6 ms | 53.3 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,409 | 15.7 ms | 64.2 ms | 111 ms | 168 ms | 0 |
| Read only | 1 | 16,643 | 0.05 ms | 0.104 ms | 0.217 ms | 0.791 ms | 0 |
| Read only | 8 | 33,219 | 0.214 ms | 0.407 ms | 0.597 ms | 1.49 ms | 0 |
| Read only | 32 | 32,963 | 0.818 ms | 1.68 ms | 2.43 ms | 4.55 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 3.29 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 | 285 | 2.9 ms | 6.33 ms | 10.2 ms | 14.9 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,154 | 5.45 ms | 13.9 ms | 25.7 ms | 41.6 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,762 | 15.1 ms | 37.2 ms | 66.9 ms | 119 ms | 0 |
| Read only | 1 | 2,591 | 0.293 ms | 0.952 ms | 1.85 ms | 3.29 ms | 0 |
| Read only | 8 | 17,914 | 0.345 ms | 0.999 ms | 1.95 ms | 3.6 ms | 0 |
| Read only | 32 | 19,136 | 1.39 ms | 3.24 ms | 5.23 ms | 9.53 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 32.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 | 34.7 | 694 | 23.1 ms | 52.9 ms | 170 ms | 0 |
| Read/write | 8 | 96.7 | 1,933 | 58.9 ms | 236 ms | 376 ms | 0 |
| Read/write | 32 | 225 | 4,492 | 105 ms | 357 ms | 570 ms | 0 |
| Read only | 1 | 595 | 9,523 | 1.55 ms | 2.52 ms | 3.96 ms | 0 |
| Read only | 8 | 1,133 | 18,121 | 6.79 ms | 10.1 ms | 12.3 ms | 0 |
| Read only | 32 | 979 | 15,661 | 31.9 ms | 43.4 ms | 51 ms | 0 |
10 tables of 100,000 rows, loaded in 50.7 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 59,167 | 53,788 | 0.647 ms | 3.62 ms | 5.31 ms |
| 1:1 set:get | 59,079 | 29,540 | 0.647 ms | 3.63 ms | 5.25 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 | 229 | 904 | 1,256 | 3.55 s |
| Express express-postgresjs | 5,016 | 6,920 | 18,353 | 443 ms |
| Fastify fastify-postgres | 5,193 | 7,628 | 19,824 | 610 ms |
| NestJS nestjs | 2,799 | 3,197 | 10,536 | 184 ms |
| Nuxt nuxt | 4,465 | 6,889 | 17,835 | 246 ms |
| FastAPI fastapi | 1,805 | 2,367 | 10,575 | 589 ms |
| Django django-postgresql | 911 | 992 | 2,789 | 452 ms |
| Rails rails | 1,474 | 2,049 | 8,150 | 248 ms |
| Laravel laravel | 342 | 356 | 685 | 862 ms |
| Symfony symfony | 432 | 501 | 1,533 | 718 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 | 1.08 | 1.48 s | 1.7 s | 1.75 s | 0% |
| Shop page | 1.08 | 1.99 s | 2.18 s | 2.24 s | 0% |
| Category page | 1.08 | 1.26 s | 2 s | 2.18 s | 0% |
| Product page | 1.08 | 1.29 s | 1.5 s | 1.58 s | 0% |
| Product search | 1.08 | 1.16 s | 1.42 s | 1.47 s | 0% |
| 32 virtual users | |||||
| Home page | 1.32 | 5.23 s | 6.13 s | 6.46 s | 0% |
| Shop page | 1.14 | 7.05 s | 8.23 s | 8.45 s | 0% |
| Category page | 0.899 | 6.6 s | 7.65 s | 8.07 s | 0% |
| Product page | 0.899 | 5.5 s | 5.95 s | 6.05 s | 0% |
| Product search | 0.899 | 4.84 s | 5.53 s | 5.67 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 2 | 1.58 s | 1.79 s | 1.92 s | 0% |
| Cart | 2 | 1.21 s | 1.47 s | 1.51 s | 0% |
| Checkout | 2 | 956 ms | 1.12 s | 1.18 s | 0% |
| 32 virtual users | |||||
| Add to cart | 2.23 | 5.09 s | 6.37 s | 6.61 s | 0% |
| Cart | 2.16 | 5.38 s | 6.03 s | 6.35 s | 0% |
| Checkout | 1.8 | 4.09 s | 4.96 s | 5.25 s | 0% |
k6 with a fixed number of virtual users, 67 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.923 | 482 ms | 615 ms | 847 ms | 0% |
| Topic JSON | 0.478 | 250 ms | 298 ms | 307 ms | 0% |
| Home page | 0.478 | 403 ms | 533 ms | 856 ms | 0% |
| Categories page | 0.231 | 483 ms | 682 ms | 707 ms | 0% |
| User activity page | 0.231 | 293 ms | 539 ms | 785 ms | 0% |
| 4 virtual users | |||||
| Topic page | 1.58 | 1.13 s | 1.8 s | 2.36 s | 0% |
| Topic JSON | 0.781 | 637 ms | 806 ms | 833 ms | 0% |
| Home page | 0.781 | 965 ms | 1.23 s | 1.36 s | 0% |
| Categories page | 0.407 | 1.1 s | 1.76 s | 2.42 s | 0% |
| User activity page | 0.391 | 659 ms | 862 ms | 892 ms | 0% |
| 16 virtual users | |||||
| Topic page | 1.36 | 2.28 s | 2.83 s | 3.09 s | 0% |
| Topic JSON | 0.681 | 1.76 s | 2.22 s | 2.37 s | 0% |
| Home page | 0.697 | 2.2 s | 3.05 s | 3.34 s | 0% |
| Categories page | 0.349 | 2.53 s | 3.31 s | 3.56 s | 0% |
| User activity page | 0.364 | 1.88 s | 2.59 s | 3.17 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 31.5 | 130 ms | 378 ms | 508 ms | 0.209% |
| Topic JSON | 15.8 | 123 ms | 359 ms | 497 ms | 0.209% |
| Home page | 15.7 | 131 ms | 384 ms | 528 ms | 0.105% |
| Categories page | 7.91 | 122 ms | 380 ms | 549 ms | 0% |
| User activity page | 7.89 | 464 ms | 719 ms | 976 ms | 0% |
k6 with a fixed number of virtual users, 61 to 63 s per level, after a 22 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 406 MB of it. The container peaked at 1,445 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 4.55 | 61.5 ms | 77.8 ms | 112 ms | 0% |
| Post page | 11.3 | 33.7 ms | 44.5 ms | 58.2 ms | 0% |
| Tag page | 2.26 | 43.1 ms | 53.1 ms | 84.7 ms | 0% |
| Author page | 2.26 | 41.8 ms | 50.3 ms | 56.2 ms | 0% |
| RSS feed | 2.26 | 48 ms | 64.3 ms | 69.3 ms | 0% |
| 4 virtual users | |||||
| Home page | 5.36 | 194 ms | 258 ms | 312 ms | 0% |
| Post page | 13.4 | 136 ms | 200 ms | 251 ms | 0% |
| Tag page | 2.68 | 125 ms | 184 ms | 230 ms | 0% |
| Author page | 2.68 | 127 ms | 188 ms | 217 ms | 0% |
| RSS feed | 2.66 | 134 ms | 198 ms | 280 ms | 0% |
| 16 virtual users | |||||
| Home page | 5.4 | 755 ms | 950 ms | 1.12 s | 0% |
| Post page | 13.5 | 611 ms | 802 ms | 913 ms | 0% |
| Tag page | 2.72 | 419 ms | 549 ms | 653 ms | 0% |
| Author page | 2.68 | 422 ms | 592 ms | 647 ms | 0% |
| RSS feed | 2.68 | 415 ms | 585 ms | 672 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 1.94 | 64.7 ms | 97.1 ms | 106 ms | 0% |
| Post editor | 5.84 | 26.4 ms | 42.9 ms | 53.9 ms | 0% |
| Saving a draft | 5.84 | 85.4 ms | 112 ms | 145 ms | 0% |
| Member list | 1.95 | 77.2 ms | 118 ms | 148 ms | 0% |
| 4 virtual users | |||||
| Post list | 2.46 | 86.2 ms | 113 ms | 151 ms | 0% |
| Post editor | 7.48 | 35.4 ms | 55.9 ms | 75.3 ms | 0% |
| Saving a draft | 7.51 | 421 ms | 548 ms | 616 ms | 0% |
| Member list | 2.51 | 98.6 ms | 144 ms | 216 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 342 MB and MySQL at 587 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 0.78 | 159 ms | 207 ms | 232 ms | 0% |
| Blog index | 0.78 | 609 ms | 784 ms | 888 ms | 0% |
| Blog post | 2.31 | 50.7 ms | 75.5 ms | 87.2 ms | 0% |
| Bread page | 2.32 | 55.3 ms | 70.6 ms | 84 ms | 0% |
| Location page | 0.78 | 54.3 ms | 74.8 ms | 79.8 ms | 0% |
| Site search | 0.764 | 95.3 ms | 155 ms | 187 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.45 | 407 ms | 560 ms | 591 ms | 0% |
| Blog index | 1.48 | 1.31 s | 1.85 s | 2.21 s | 0% |
| Blog post | 4.34 | 108 ms | 201 ms | 317 ms | 0% |
| Bread page | 4.37 | 115 ms | 188 ms | 228 ms | 0% |
| Location page | 1.48 | 109 ms | 169 ms | 206 ms | 0% |
| Site search | 1.43 | 166 ms | 383 ms | 429 ms | 0% |
| 16 virtual users | |||||
| Home page | 1.61 | 1.14 s | 1.57 s | 1.7 s | 0% |
| Blog index | 1.65 | 2.91 s | 3.35 s | 3.91 s | 0% |
| Blog post | 4.75 | 660 ms | 1.01 s | 1.1 s | 0% |
| Bread page | 4.82 | 662 ms | 1.03 s | 1.2 s | 0% |
| Location page | 1.64 | 641 ms | 1 s | 1.08 s | 0% |
| Site search | 1.56 | 753 ms | 1.18 s | 1.34 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.376 | 174 ms | 219 ms | 226 ms | 0% |
| Page explorer | 0.768 | 606 ms | 897 ms | 956 ms | 0% |
| Page editor | 1.13 | 286 ms | 380 ms | 478 ms | 0% |
| Image library | 0.376 | 108 ms | 169 ms | 1.08 s | 0% |
| Admin page search | 0.376 | 70.7 ms | 147 ms | 156 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.608 | 412 ms | 827 ms | 912 ms | 0% |
| Page explorer | 1.25 | 1.52 s | 2.35 s | 2.54 s | 0% |
| Page editor | 1.89 | 706 ms | 1.16 s | 1.51 s | 0% |
| Image library | 0.641 | 296 ms | 656 ms | 796 ms | 0% |
| Admin page search | 0.625 | 148 ms | 461 ms | 499 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 178 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 6.4% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 20 GB SSD | 18 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
- AMD EPYC 7282 16-Core Processor
- CPU cores
- 2
- CPU frequency
- 2800 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- Yes
- RAM reported
- 1.9 GiB
- Swap reported
- 0 MiB
- Disk reported
- 18 GiB
- Virtualization reported
- KVM
- CPU steal
- 6.4% of busy CPU time stolen
- Distro
- Ubuntu 24.04.5 LTS
- Kernel
- 6.8.0-142-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- No
Advertised at test time
- Plan
- DEV1-S
- Product line
- Development
- Location
- Paris 2
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 20 GB SSD
- Virtualization
- KVM
- Network
- 200 Mbps
- Transfer
- Unmetered
- Port 25
- Unknown
- Monthly price at test time
- €6.55 EUR
- Hourly price at test time
- €0.0090 EUR
- YABS version
- v2026-09-20
- Ran at
- Oct 15, 2026, 00:02:32 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 15, 2026, 00:01:00 UTC
- First update from the server
- Oct 15, 2026, 00:01:54 UTC
- Completed
- Oct 15, 2026, 01:44:00 UTC
- Server deleted
- Oct 15, 2026, 01:44:00 UTC
- Cost of this run
- €0.015 EUR
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.