Scaleway DEV1-S
Server
-
ProviderScaleway
-
PlanDEV1-S
-
LocationAmsterdam 1
-
vCPU2
-
RAM2 GB
-
Storage20 GB SSD
-
Network200 Mbps
-
OS imageubuntu_noble
-
TriggerScheduled
-
Queued atOct 14, 2026, 00:28:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 956 | 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,130
|
Single-core only |
| Navigation |
1,083
|
Single-core only |
| HTML5 Browser |
851
|
Single-core only |
| PDF Viewer |
1,072
|
Single-core only |
| Photo Library |
945
|
Single-core only |
| Clang |
801
|
Single-core only |
| Text Processing |
797
|
Single-core only |
| Asset Compression |
951
|
Single-core only |
| HDR |
842
|
Single-core only |
| Photo Editor |
1,063
|
Single-core only |
| Ray Tracer |
884
|
Single-core only |
| Structure from Motion |
1,182
|
Single-core only |
| Game Physics |
889
|
Single-core only |
| Video Encoder |
878
|
Single-core only |
| Audio Encoder |
1,044
|
Single-core only |
| Video Player |
989
|
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 | 29.8 GB/s | 3 | 6.63% |
| Scale higher is better | 23.3 GB/s | 3 | 4.24% |
| Add higher is better | 24.8 GB/s | 3 | 3.22% |
| Triad higher is better | 24.8 GB/s | 3 | 3.72% |
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 | 374/s | 3 | 0.708% |
| RSA 4096 verifies higher is better | 24,070/s | 3 | 1.25% |
| SHA-256 higher is better | 1.11 GB/s | 3 | 0.364% |
| AES-256-GCM higher is better | 5.6 GB/s | 3 | 0.903% |
| ChaCha20-Poly1305 higher is better | 3.15 GB/s | 3 | 1.34% |
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.14 ms | 3 | 0.622% |
| Requests per second, 90th percentile higher is better | 383/s | 3 | 0.399% |
| Request latency, 99.9th percentile lower is better | 9.78 ms | 3 | 2.04% |
| Requests per second, average higher is better | 373/s | 3 | 0.468% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 164.1 MB/s (41,998 IOPS) | 164.5 MB/s (42,109 IOPS) | 328.5 MB/s (84,107 IOPS) |
| 64K | 1.71 GB/s (27,981 IOPS) | 1.72 GB/s (28,128 IOPS) | 3.42 GB/s (56,109 IOPS) |
| 512K | 1.98 GB/s (4,046 IOPS) | 2.08 GB/s (4,261 IOPS) | 4.06 GB/s (8,307 IOPS) |
| 1M | 2.1 GB/s (2,147 IOPS) | 2.24 GB/s (2,290 IOPS) | 4.33 GB/s (4,437 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 | 453 Mbps | 2.79 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 416 Mbps | 7.5 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 439 Mbps | 1.51 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 433 Mbps | 1.35 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 448 Mbps | 3.2 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 | 249 | 4.02 ms |
| fdatasync | 252 | 3.97 ms |
| fsync | 93.5 | 10.7 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 113 | 8.88 ms |
| Two 8 kB writes | ||
| open_datasync | 120 | 8.35 ms |
| fdatasync | 216 | 4.63 ms |
| fsync | 112 | 8.96 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 58 | 17.2 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 108 | 9.24 ms |
| 2 * 8kB open_sync writes | 41.1 | 24.3 ms |
| 4 * 4kB open_sync writes | 26.2 | 38.2 ms |
| 8 * 2kB open_sync writes | 13.5 | 74.2 ms |
| 16 * 1kB open_sync writes | 7.04 | 142 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 116 | 8.65 ms |
| write, close, fsync | 120 | 8.32 ms |
| Non-synced 8 kB writes | ||
| write | 920,056 | 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 | 192 | 4.56 ms | 7.64 ms | 11.2 ms | 17.1 ms | 0 |
| Read/write (TPC-B like) | 8 | 549 | 11.4 ms | 30.6 ms | 51.1 ms | 468 ms | 0 |
| Read/write (TPC-B like) | 32 | 785 | 26.5 ms | 117 ms | 216 ms | 622 ms | 0 |
| Read only | 1 | 19,317 | 0.046 ms | 0.087 ms | 0.139 ms | 0.37 ms | 0 |
| Read only | 8 | 40,241 | 0.177 ms | 0.328 ms | 0.442 ms | 0.869 ms | 0 |
| Read only | 32 | 40,048 | 0.68 ms | 1.23 ms | 1.68 ms | 3.05 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 5.4 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 | 169 | 5.09 ms | 8.74 ms | 16 ms | 31.8 ms | 0 |
| Read/write (TPC-B like) | 8 | 534 | 10.8 ms | 33.1 ms | 94.3 ms | 204 ms | 0 |
| Read/write (TPC-B like) | 32 | 885 | 25.2 ms | 104 ms | 218 ms | 361 ms | 0 |
| Read only | 1 | 3,472 | 0.237 ms | 0.56 ms | 1.06 ms | 2.17 ms | 0 |
| Read only | 8 | 22,716 | 0.285 ms | 0.724 ms | 1.23 ms | 2.77 ms | 0 |
| Read only | 32 | 24,736 | 1.08 ms | 2.37 ms | 3.56 ms | 6.82 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 42.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.1 | 682 | 20.7 ms | 69.3 ms | 227 ms | 0 |
| Read/write | 8 | 95.8 | 1,917 | 53.9 ms | 263 ms | 435 ms | 0 |
| Read/write | 32 | 234 | 4,677 | 94.1 ms | 363 ms | 612 ms | 0 |
| Read only | 1 | 637 | 10,197 | 1.5 ms | 2.18 ms | 3.02 ms | 0 |
| Read only | 8 | 1,251 | 20,021 | 6.1 ms | 9.22 ms | 10.8 ms | 0 |
| Read only | 32 | 1,130 | 18,080 | 27.7 ms | 36.9 ms | 41.9 ms | 0 |
10 tables of 100,000 rows, loaded in 64.4 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 61,654 | 56,049 | 0.631 ms | 3.54 ms | 5.02 ms |
| 1:1 set:get | 62,055 | 31,027 | 0.615 ms | 3.54 ms | 5.09 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 | 274 | 1,022 | 1,472 | 2.33 s |
| Express express-postgresjs | 5,757 | 8,006 | 21,103 | 77 ms |
| Fastify fastify-postgres | 5,501 | 8,413 | 21,578 | 221 ms |
| NestJS nestjs | 3,339 | 3,731 | 12,595 | 137 ms |
| Nuxt nuxt | 4,715 | 7,250 | 20,276 | 402 ms |
| FastAPI fastapi | 2,715 | 3,428 | 12,347 | 421 ms |
| Django django-postgresql | 1,318 | 1,503 | 3,729 | 383 ms |
| Rails rails | 2,151 | 3,013 | 11,333 | 175 ms |
| Laravel laravel | 488 | 538 | 1,107 | 560 ms |
| Symfony symfony | 623 | 677 | 2,234 | 456 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 | 1.42 | 1.12 s | 1.28 s | 1.37 s | 0% |
| Shop page | 1.42 | 1.53 s | 1.71 s | 1.83 s | 0% |
| Category page | 1.42 | 949 ms | 1.51 s | 1.6 s | 0% |
| Product page | 1.42 | 1.02 s | 1.17 s | 1.29 s | 0% |
| Product search | 1.42 | 865 ms | 1.02 s | 1.06 s | 0% |
| 32 virtual users | |||||
| Home page | 1.42 | 4.03 s | 4.58 s | 4.66 s | 0% |
| Shop page | 1.42 | 5.55 s | 6.33 s | 6.49 s | 0% |
| Category page | 1.42 | 4.78 s | 5.58 s | 5.76 s | 0% |
| Product page | 1.42 | 4.05 s | 4.44 s | 4.54 s | 0% |
| Product search | 1.42 | 3.81 s | 4.08 s | 4.12 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 2.77 | 1.2 s | 1.42 s | 1.48 s | 0% |
| Cart | 2.77 | 946 ms | 1.13 s | 1.62 s | 0% |
| Checkout | 2.77 | 728 ms | 849 ms | 871 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 2.78 | 3.88 s | 4.78 s | 4.98 s | 0% |
| Cart | 2.78 | 4.17 s | 4.57 s | 4.75 s | 0% |
| Checkout | 2.78 | 3.18 s | 3.74 s | 3.89 s | 0% |
k6 with a fixed number of virtual users, 62 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 | 1.4 | 320 ms | 377 ms | 667 ms | 0% |
| Topic JSON | 0.707 | 172 ms | 304 ms | 330 ms | 0% |
| Home page | 0.707 | 280 ms | 312 ms | 318 ms | 0% |
| Categories page | 0.362 | 332 ms | 353 ms | 629 ms | 0% |
| User activity page | 0.345 | 194 ms | 227 ms | 447 ms | 0% |
| 4 virtual users | |||||
| Topic page | 2.17 | 816 ms | 1.15 s | 1.79 s | 0% |
| Topic JSON | 1.07 | 440 ms | 550 ms | 607 ms | 0% |
| Home page | 1.07 | 729 ms | 951 ms | 1.14 s | 0% |
| Categories page | 0.558 | 810 ms | 1.01 s | 1.15 s | 0% |
| User activity page | 0.525 | 524 ms | 704 ms | 942 ms | 0% |
| 16 virtual users | |||||
| Topic page | 1.98 | 1.98 s | 2.64 s | 2.82 s | 0% |
| Topic JSON | 1.01 | 1.57 s | 1.93 s | 2.1 s | 0% |
| Home page | 0.965 | 1.86 s | 2.6 s | 2.88 s | 0% |
| Categories page | 0.547 | 2.05 s | 2.44 s | 2.47 s | 0% |
| User activity page | 0.482 | 1.66 s | 1.94 s | 2.09 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 42.2 | 97.7 ms | 265 ms | 605 ms | 0% |
| Topic JSON | 21.2 | 100 ms | 274 ms | 587 ms | 0% |
| Home page | 21.2 | 97.2 ms | 259 ms | 529 ms | 0% |
| Categories page | 10.6 | 95.7 ms | 278 ms | 518 ms | 0% |
| User activity page | 10.6 | 319 ms | 663 ms | 1.12 s | 0% |
k6 with a fixed number of virtual users, 60 to 62 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 423 MB of it. The container peaked at 1,459 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 5.66 | 50.2 ms | 58.4 ms | 79.6 ms | 0% |
| Post page | 14.1 | 26.8 ms | 32.7 ms | 49.7 ms | 0% |
| Tag page | 2.83 | 34.3 ms | 40.9 ms | 62.5 ms | 0% |
| Author page | 2.81 | 34.3 ms | 41.4 ms | 56 ms | 0% |
| RSS feed | 2.81 | 41.3 ms | 50 ms | 58.8 ms | 0% |
| 4 virtual users | |||||
| Home page | 6.6 | 157 ms | 208 ms | 287 ms | 0% |
| Post page | 16.5 | 112 ms | 155 ms | 203 ms | 0% |
| Tag page | 3.31 | 95.5 ms | 138 ms | 180 ms | 0% |
| Author page | 3.28 | 101 ms | 149 ms | 165 ms | 0% |
| RSS feed | 3.28 | 111 ms | 175 ms | 207 ms | 0% |
| 16 virtual users | |||||
| Home page | 6.69 | 598 ms | 731 ms | 782 ms | 0% |
| Post page | 16.7 | 504 ms | 624 ms | 664 ms | 0% |
| Tag page | 3.33 | 329 ms | 419 ms | 468 ms | 0% |
| Author page | 3.36 | 326 ms | 412 ms | 469 ms | 0% |
| RSS feed | 3.31 | 339 ms | 430 ms | 453 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 2.27 | 49.6 ms | 67.5 ms | 90.3 ms | 0% |
| Post editor | 6.8 | 19.4 ms | 26 ms | 31.9 ms | 0% |
| Saving a draft | 6.8 | 81.5 ms | 111 ms | 134 ms | 0% |
| Member list | 2.27 | 63.2 ms | 78.6 ms | 97.6 ms | 0% |
| 4 virtual users | |||||
| Post list | 2.84 | 58.7 ms | 71.9 ms | 103 ms | 0% |
| Post editor | 8.55 | 24.4 ms | 35 ms | 52.1 ms | 0% |
| Saving a draft | 8.58 | 383 ms | 472 ms | 522 ms | 0% |
| Member list | 2.84 | 70.9 ms | 81.9 ms | 110 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 349 MB and MySQL at 587 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.06 | 123 ms | 136 ms | 137 ms | 0% |
| Blog index | 1.06 | 435 ms | 487 ms | 514 ms | 0% |
| Blog post | 3.18 | 39.4 ms | 60 ms | 63.9 ms | 0% |
| Bread page | 3.18 | 42.5 ms | 49.2 ms | 55.9 ms | 0% |
| Location page | 1.06 | 41.3 ms | 47.6 ms | 52 ms | 0% |
| Site search | 1.05 | 69.4 ms | 125 ms | 135 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.79 | 310 ms | 435 ms | 447 ms | 0% |
| Blog index | 1.84 | 1.02 s | 1.38 s | 1.46 s | 0% |
| Blog post | 5.47 | 88.4 ms | 153 ms | 191 ms | 0% |
| Bread page | 5.47 | 97.8 ms | 142 ms | 158 ms | 0% |
| Location page | 1.84 | 87.6 ms | 140 ms | 160 ms | 0% |
| Site search | 1.82 | 142 ms | 284 ms | 315 ms | 0% |
| 16 virtual users | |||||
| Home page | 1.92 | 970 ms | 1.2 s | 1.24 s | 0% |
| Blog index | 2 | 2.38 s | 2.76 s | 2.96 s | 0% |
| Blog post | 5.75 | 545 ms | 806 ms | 925 ms | 0% |
| Bread page | 5.81 | 560 ms | 863 ms | 990 ms | 0% |
| Location page | 1.96 | 544 ms | 852 ms | 1.06 s | 0% |
| Site search | 1.93 | 683 ms | 988 ms | 1.11 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.462 | 129 ms | 150 ms | 154 ms | 0% |
| Page explorer | 0.923 | 509 ms | 554 ms | 791 ms | 0% |
| Page editor | 1.39 | 241 ms | 294 ms | 499 ms | 0% |
| Image library | 0.462 | 89.4 ms | 106 ms | 928 ms | 0% |
| Admin page search | 0.462 | 50.7 ms | 114 ms | 114 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.765 | 361 ms | 616 ms | 682 ms | 0% |
| Page explorer | 1.58 | 1.2 s | 1.87 s | 1.93 s | 0% |
| Page editor | 2.34 | 552 ms | 998 ms | 1.14 s | 0% |
| Image library | 0.765 | 299 ms | 655 ms | 762 ms | 0% |
| Admin page search | 0.765 | 120 ms | 433 ms | 465 ms | 0% |
k6 with a fixed number of virtual users, 60 to 61 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 176 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 3.5% 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
- 3.5% 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
- Amsterdam 1
- 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 14, 2026, 00:29:24 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 14, 2026, 00:28:00 UTC
- Server created
- Oct 14, 2026, 00:28:52 UTC
- First update from the server
- Oct 14, 2026, 00:28:52 UTC
- Completed
- Oct 14, 2026, 02:11:00 UTC
- Server deleted
- Oct 14, 2026, 02:11: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.