Scaleway DEV1-S
Server
-
ProviderScaleway
-
PlanDEV1-S
-
LocationWarsaw 1
-
vCPU2
-
RAM2 GB
-
Storage20 GB SSD
-
Network200 Mbps
-
OS imageubuntu_noble
-
TriggerScheduled
-
Queued atOct 15, 2026, 19:16:00 UTC
Latest runs of this plan
Full history of this planCPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 730 | 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 |
930
|
Single-core only |
| Navigation |
928
|
Single-core only |
| HTML5 Browser |
668
|
Single-core only |
| PDF Viewer |
830
|
Single-core only |
| Photo Library |
611
|
Single-core only |
| Clang |
651
|
Single-core only |
| Text Processing |
634
|
Single-core only |
| Asset Compression |
712
|
Single-core only |
| HDR |
620
|
Single-core only |
| Photo Editor |
623
|
Single-core only |
| Ray Tracer |
784
|
Single-core only |
| Structure from Motion |
833
|
Single-core only |
| Game Physics |
698
|
Single-core only |
| Video Encoder |
704
|
Single-core only |
| Audio Encoder |
830
|
Single-core only |
| Video Player |
730
|
Single-core only |
Rank among the 191 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 | 25.5 GB/s | 3 | 1.91% |
| Scale higher is better | 17.4 GB/s | 3 | 2.41% |
| Add higher is better | 19.3 GB/s | 3 | 3% |
| Triad higher is better | 19.3 GB/s | 3 | 2.9% |
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 | 243/s | 3 | 3.24% |
| RSA 4096 verifies higher is better | 16,410/s | 3 | 0.816% |
| SHA-256 higher is better | 990 MB/s | 3 | 0.88% |
| AES-256-GCM higher is better | 4.94 GB/s | 3 | 2.79% |
| ChaCha20-Poly1305 higher is better | 1.53 GB/s | 3 | 0.395% |
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.72 ms | 3 | 0.485% |
| Requests per second, 90th percentile higher is better | 345/s | 3 | 0.58% |
| Request latency, 99.9th percentile lower is better | 12.2 ms | 3 | 9.39% |
| Requests per second, average higher is better | 340/s | 3 | 0.286% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 125.1 MB/s (32,022 IOPS) | 125.4 MB/s (32,106 IOPS) | 250.5 MB/s (64,128 IOPS) |
| 64K | 1.26 GB/s (20,645 IOPS) | 1.27 GB/s (20,754 IOPS) | 2.53 GB/s (41,399 IOPS) |
| 512K | 1.41 GB/s (2,889 IOPS) | 1.49 GB/s (3,042 IOPS) | 2.9 GB/s (5,931 IOPS) |
| 1M | 1.35 GB/s (1,381 IOPS) | 1.44 GB/s (1,473 IOPS) | 2.79 GB/s (2,854 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 | 4.43 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 456 Mbps | 5.76 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 435 Mbps | 1.34 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 431 Mbps | 1.2 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 446 Mbps | 2.29 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 | 492 | 2.03 ms |
| fdatasync | 501 | 2 ms |
| fsync | 205 | 4.88 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 202 | 4.95 ms |
| Two 8 kB writes | ||
| open_datasync | 251 | 3.99 ms |
| fdatasync | 445 | 2.25 ms |
| fsync | 197 | 5.09 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 103 | 9.71 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 201 | 4.98 ms |
| 2 * 8kB open_sync writes | 107 | 9.33 ms |
| 4 * 4kB open_sync writes | 53.1 | 18.8 ms |
| 8 * 2kB open_sync writes | 26.9 | 37.2 ms |
| 16 * 1kB open_sync writes | 14.1 | 71.1 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 213 | 4.69 ms |
| write, close, fsync | 217 | 4.61 ms |
| Non-synced 8 kB writes | ||
| write | 636,184 | 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 | 295 | 3.16 ms | 5.05 ms | 6.8 ms | 16.5 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,090 | 5.96 ms | 15.9 ms | 23.7 ms | 37.5 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,425 | 15.8 ms | 63.4 ms | 104 ms | 196 ms | 0 |
| Read only | 1 | 13,982 | 0.066 ms | 0.097 ms | 0.118 ms | 0.185 ms | 0 |
| Read only | 8 | 29,749 | 0.245 ms | 0.411 ms | 0.51 ms | 1 ms | 0 |
| Read only | 32 | 27,943 | 1.01 ms | 1.9 ms | 2.46 ms | 3.93 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 3.62 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 | 247 | 3.79 ms | 6.2 ms | 11.1 ms | 21.6 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,100 | 5.37 ms | 15.9 ms | 34.7 ms | 57.8 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,729 | 14.7 ms | 41.8 ms | 79.8 ms | 144 ms | 0 |
| Read only | 1 | 2,855 | 0.308 ms | 0.617 ms | 1.13 ms | 2.35 ms | 0 |
| Read only | 8 | 16,590 | 0.399 ms | 0.943 ms | 1.55 ms | 3.11 ms | 0 |
| Read only | 32 | 16,701 | 1.67 ms | 3.36 ms | 4.61 ms | 8.12 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 38.2 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 | 39.1 | 782 | 21.1 ms | 48.3 ms | 123 ms | 0 |
| Read/write | 8 | 114 | 2,285 | 54.8 ms | 150 ms | 272 ms | 0 |
| Read/write | 32 | 251 | 5,013 | 109 ms | 267 ms | 383 ms | 0 |
| Read only | 1 | 512 | 8,185 | 1.93 ms | 2.48 ms | 2.86 ms | 0 |
| Read only | 8 | 945 | 15,126 | 8.13 ms | 12.3 ms | 14.5 ms | 0 |
| Read only | 32 | 868 | 13,892 | 36.2 ms | 48.3 ms | 57.9 ms | 0 |
10 tables of 100,000 rows, loaded in 45.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,382 | 45,802 | 0.959 ms | 3.52 ms | 5.22 ms |
| 1:1 set:get | 48,758 | 24,379 | 0.991 ms | 3.58 ms | 5.31 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 | 205 | 703 | 881 | 4.32 s |
| Express express-postgresjs | 4,650 | 6,629 | 15,847 | 304 ms |
| Fastify fastify-postgres | 4,543 | 7,162 | 16,164 | 346 ms |
| NestJS nestjs | 2,396 | 2,505 | 9,828 | 182 ms |
| Nuxt nuxt | 3,934 | 6,103 | 14,180 | 600 ms |
| FastAPI fastapi | 1,894 | 2,396 | 9,783 | 666 ms |
| Django django-postgresql | 871 | 1,052 | 2,528 | 465 ms |
| Rails rails | 1,536 | 2,175 | 8,645 | 238 ms |
| Laravel laravel | 405 | 426 | 745 | 675 ms |
| Symfony symfony | 502 | 544 | 1,444 | 615 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.19 | 1.34 s | 1.54 s | 1.58 s | 0% |
| Shop page | 1.19 | 1.79 s | 2.02 s | 2.12 s | 0% |
| Category page | 1.19 | 1.08 s | 1.81 s | 2.01 s | 0% |
| Product page | 1.19 | 1.24 s | 1.43 s | 1.54 s | 0% |
| Product search | 1.19 | 1.09 s | 1.26 s | 1.36 s | 0% |
| 32 virtual users | |||||
| Home page | 1.35 | 4.59 s | 5.45 s | 5.64 s | 0% |
| Shop page | 1.35 | 6.47 s | 7.44 s | 7.66 s | 0% |
| Category page | 1.32 | 5.75 s | 6.85 s | 7.35 s | 0% |
| Product page | 0.929 | 4.7 s | 5.03 s | 5.12 s | 0% |
| Product search | 0.9 | 4.43 s | 4.74 s | 4.83 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 2.28 | 1.4 s | 1.63 s | 1.74 s | 0% |
| Cart | 2.28 | 1.12 s | 1.29 s | 1.44 s | 0% |
| Checkout | 2.28 | 839 ms | 1.01 s | 1.06 s | 0% |
| 32 virtual users | |||||
| Add to cart | 2.4 | 4.43 s | 5.54 s | 5.74 s | 0% |
| Cart | 2.4 | 4.78 s | 5.31 s | 5.52 s | 0% |
| Checkout | 2.4 | 3.71 s | 4.25 s | 4.36 s | 0% |
k6 with a fixed number of virtual users, 65 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 | 1.09 | 410 ms | 602 ms | 725 ms | 0% |
| Topic JSON | 0.543 | 217 ms | 253 ms | 257 ms | 0% |
| Home page | 0.543 | 373 ms | 573 ms | 702 ms | 0% |
| Categories page | 0.28 | 424 ms | 492 ms | 504 ms | 0% |
| User activity page | 0.263 | 250 ms | 281 ms | 315 ms | 0% |
| 4 virtual users | |||||
| Topic page | 2 | 864 ms | 1.22 s | 1.68 s | 0% |
| Topic JSON | 1.03 | 476 ms | 575 ms | 616 ms | 0% |
| Home page | 1.02 | 773 ms | 1.25 s | 1.74 s | 0% |
| Categories page | 0.525 | 896 ms | 1.16 s | 1.18 s | 0% |
| User activity page | 0.509 | 527 ms | 826 ms | 970 ms | 0% |
| 16 virtual users | |||||
| Topic page | 2.06 | 2.16 s | 2.52 s | 2.93 s | 0% |
| Topic JSON | 1.05 | 1.78 s | 2.22 s | 2.24 s | 0% |
| Home page | 1.01 | 2.08 s | 2.43 s | 2.74 s | 0% |
| Categories page | 0.499 | 2.02 s | 2.54 s | 2.65 s | 0% |
| User activity page | 0.515 | 1.91 s | 2.31 s | 2.43 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 42.5 | 102 ms | 255 ms | 445 ms | 0% |
| Topic JSON | 21.3 | 97.5 ms | 239 ms | 361 ms | 0% |
| Home page | 21.3 | 102 ms | 254 ms | 418 ms | 0% |
| Categories page | 10.7 | 109 ms | 249 ms | 410 ms | 0% |
| User activity page | 10.7 | 329 ms | 585 ms | 779 ms | 0% |
k6 with a fixed number of virtual users, 61 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 385 MB of it. The container peaked at 1,419 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 4.56 | 61.5 ms | 79.3 ms | 96.3 ms | 0% |
| Post page | 11.4 | 32.5 ms | 44.6 ms | 55 ms | 0% |
| Tag page | 2.28 | 42.2 ms | 53.8 ms | 56.7 ms | 0% |
| Author page | 2.28 | 43.2 ms | 56.2 ms | 67.2 ms | 0% |
| RSS feed | 2.26 | 49.2 ms | 63.2 ms | 73.8 ms | 0% |
| 4 virtual users | |||||
| Home page | 5.24 | 199 ms | 262 ms | 302 ms | 0% |
| Post page | 13.1 | 139 ms | 201 ms | 251 ms | 0% |
| Tag page | 2.64 | 126 ms | 185 ms | 225 ms | 0% |
| Author page | 2.63 | 130 ms | 179 ms | 201 ms | 0% |
| RSS feed | 2.61 | 144 ms | 194 ms | 236 ms | 0% |
| 16 virtual users | |||||
| Home page | 5.33 | 755 ms | 901 ms | 958 ms | 0% |
| Post page | 13.3 | 634 ms | 760 ms | 824 ms | 0% |
| Tag page | 2.65 | 400 ms | 531 ms | 595 ms | 0% |
| Author page | 2.68 | 409 ms | 513 ms | 601 ms | 0% |
| RSS feed | 2.65 | 420 ms | 567 ms | 606 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 2.12 | 61.7 ms | 77.6 ms | 95.1 ms | 0% |
| Post editor | 6.39 | 24.7 ms | 34.5 ms | 43.2 ms | 0% |
| Saving a draft | 6.39 | 76.6 ms | 94.5 ms | 119 ms | 0% |
| Member list | 2.12 | 76.8 ms | 97.1 ms | 116 ms | 0% |
| 4 virtual users | |||||
| Post list | 2.78 | 80.6 ms | 100 ms | 167 ms | 0% |
| Post editor | 8.42 | 31.9 ms | 46.8 ms | 56.9 ms | 0% |
| Saving a draft | 8.45 | 377 ms | 472 ms | 529 ms | 0% |
| Member list | 2.81 | 94.5 ms | 122 ms | 149 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 343 MB and MySQL at 583 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 0.781 | 165 ms | 186 ms | 191 ms | 0% |
| Blog index | 0.781 | 599 ms | 643 ms | 655 ms | 0% |
| Blog post | 2.33 | 53.2 ms | 84.1 ms | 93.6 ms | 0% |
| Bread page | 2.34 | 58.3 ms | 73 ms | 78.8 ms | 0% |
| Location page | 0.781 | 55.3 ms | 71.4 ms | 73.6 ms | 0% |
| Site search | 0.781 | 88.8 ms | 169 ms | 187 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.5 | 349 ms | 535 ms | 568 ms | 0% |
| Blog index | 1.55 | 1.32 s | 1.73 s | 1.83 s | 0% |
| Blog post | 4.53 | 103 ms | 168 ms | 204 ms | 0% |
| Bread page | 4.56 | 112 ms | 167 ms | 201 ms | 0% |
| Location page | 1.55 | 107 ms | 161 ms | 179 ms | 0% |
| Site search | 1.52 | 166 ms | 292 ms | 380 ms | 0% |
| 16 virtual users | |||||
| Home page | 1.62 | 1.09 s | 1.47 s | 1.63 s | 0% |
| Blog index | 1.75 | 2.79 s | 3.3 s | 3.46 s | 0% |
| Blog post | 5.01 | 615 ms | 1.06 s | 1.24 s | 0% |
| Bread page | 5.05 | 623 ms | 1 s | 1.21 s | 0% |
| Location page | 1.7 | 589 ms | 969 ms | 1.25 s | 0% |
| Site search | 1.65 | 737 ms | 1.21 s | 1.49 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.362 | 168 ms | 199 ms | 235 ms | 0% |
| Page explorer | 0.757 | 632 ms | 720 ms | 760 ms | 0% |
| Page editor | 1.1 | 294 ms | 373 ms | 454 ms | 0% |
| Image library | 0.362 | 120 ms | 156 ms | 1.2 s | 0% |
| Admin page search | 0.362 | 77.1 ms | 135 ms | 205 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.653 | 449 ms | 886 ms | 969 ms | 0% |
| Page explorer | 1.32 | 1.51 s | 2.41 s | 2.74 s | 0% |
| Page editor | 2.01 | 658 ms | 1.28 s | 1.33 s | 0% |
| Image library | 0.669 | 323 ms | 638 ms | 779 ms | 0% |
| Admin page search | 0.653 | 140 ms | 325 ms | 468 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 293 MB, Postgres at 176 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 1% 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 7281 16-Core Processor
- CPU cores
- 2
- CPU frequency
- 2096 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
- 1% 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
- Warsaw 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 15, 2026, 19:18:14 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 15, 2026, 19:16:00 UTC
- Server created
- Oct 15, 2026, 19:16:58 UTC
- First update from the server
- Oct 15, 2026, 19:16:58 UTC
- Completed
- Oct 15, 2026, 21:00:00 UTC
- Server deleted
- Oct 15, 2026, 21:00:00 UTC
- Cost of this run
- €0.016 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.