Gcore CPU-Optimized G2 2 vCPU / 2 GB
Manassas
Server
-
ProviderGcore
-
PlanCPU-Optimized G2 2 vCPU / 2 GB
-
LocationManassas
-
vCPU2
-
RAM2 GB
-
Storage
-
Network1 Gbps
-
OS imageubuntu-24.04
-
TriggerScheduled
-
Queued atOct 16, 2026, 03:50:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,170 | 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,074
|
Single-core only |
| Navigation |
1,349
|
Single-core only |
| HTML5 Browser |
1,196
|
Single-core only |
| PDF Viewer |
1,338
|
Single-core only |
| Photo Library |
1,073
|
Single-core only |
| Clang |
1,142
|
Single-core only |
| Text Processing |
1,163
|
Single-core only |
| Asset Compression |
880
|
Single-core only |
| HDR |
1,062
|
Single-core only |
| Photo Editor |
1,425
|
Single-core only |
| Ray Tracer |
1,136
|
Single-core only |
| Structure from Motion |
1,398
|
Single-core only |
| Game Physics |
1,094
|
Single-core only |
| Video Encoder |
1,133
|
Single-core only |
| Audio Encoder |
1,093
|
Single-core only |
| Video Player |
1,301
|
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 | 45.7 GB/s | 3 | 2.25% |
| Scale higher is better | 25.4 GB/s | 3 | 0.874% |
| Add higher is better | 27 GB/s | 3 | 0.234% |
| Triad higher is better | 27.2 GB/s | 3 | 0.977% |
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 | 387/s | 3 | 0.176% |
| RSA 4096 verifies higher is better | 24,867/s | 3 | 0.449% |
| SHA-256 higher is better | 450 MB/s | 3 | 0.413% |
| AES-256-GCM higher is better | 18.5 GB/s | 3 | 0.593% |
| ChaCha20-Poly1305 higher is better | 4.98 GB/s | 3 | 0.59% |
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.25 ms | 3 | 0% |
| Requests per second, 90th percentile higher is better | 471/s | 3 | 0.123% |
| Request latency, 99.9th percentile lower is better | 7.45 ms | 3 | 7.66% |
| Requests per second, average higher is better | 469/s | 3 | 0.0444% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 2.3 MB/s (598 IOPS) | 2.4 MB/s (604 IOPS) | 4.7 MB/s (1,202 IOPS) |
| 64K | 37.4 MB/s (599 IOPS) | 37.8 MB/s (604 IOPS) | 75.2 MB/s (1,203 IOPS) |
| 512K | 48.7 MB/s (97 IOPS) | 51.6 MB/s (103 IOPS) | 100.3 MB/s (200 IOPS) |
| 1M | 48.6 MB/s (48 IOPS) | 51.7 MB/s (51 IOPS) | 100.3 MB/s (99 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 | 1.21 Gbps | 1.35 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.41 Gbps | 1.37 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 568 Mbps | 900 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.4 Gbps | 1.4 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.5 Gbps | 1.45 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 | 453 | 2.21 ms |
| fdatasync | 406 | 2.46 ms |
| fsync | 149 | 6.72 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 150 | 6.67 ms |
| Two 8 kB writes | ||
| open_datasync | 217 | 4.61 ms |
| fdatasync | 414 | 2.41 ms |
| fsync | 137 | 7.28 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 61.8 | 16.2 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 151 | 6.61 ms |
| 2 * 8kB open_sync writes | 66.9 | 14.9 ms |
| 4 * 4kB open_sync writes | 35.3 | 28.3 ms |
| 8 * 2kB open_sync writes | 21.3 | 47 ms |
| 16 * 1kB open_sync writes | 6.59 | 152 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 111 | 8.99 ms |
| write, close, fsync | 130 | 7.68 ms |
| Non-synced 8 kB writes | ||
| write | 836,793 | 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 | 366 | 1.98 ms | 5.8 ms | 11.6 ms | 116 ms | 0 |
| Read/write (TPC-B like) | 8 | 927 | 5.16 ms | 19.7 ms | 60.9 ms | 531 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,319 | 11.5 ms | 85.6 ms | 205 ms | 675 ms | 0 |
| Read only | 1 | 28,846 | 0.034 ms | 0.043 ms | 0.05 ms | 0.079 ms | 0 |
| Read only | 8 | 56,159 | 0.13 ms | 0.205 ms | 0.244 ms | 0.467 ms | 0 |
| Read only | 32 | 53,697 | 0.515 ms | 0.763 ms | 1.05 ms | 1.95 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 3.81 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 | 249 | 2.49 ms | 5.86 ms | 14.7 ms | 169 ms | 0 |
| Read/write (TPC-B like) | 8 | 371 | 11.8 ms | 84.5 ms | 172 ms | 327 ms | 0 |
| Read/write (TPC-B like) | 32 | 354 | 71.7 ms | 256 ms | 383 ms | 592 ms | 0 |
| Read only | 1 | 601 | 1.06 ms | 4.58 ms | 7.61 ms | 15.5 ms | 0 |
| Read only | 8 | 522 | 8.26 ms | 43.4 ms | 166 ms | 283 ms | 0 |
| Read only | 32 | 76.4 | 359 ms | 966 ms | 1.17 s | n/a | 0 |
Scale 100 (10,000,000 accounts), loaded in 77.3 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 | 4.59 | 91.8 | 109 ms | 658 ms | 733 ms | 0 |
| Read/write | 8 | 7.51 | 150 | 943 ms | 2.59 s | 3.64 s | 0 |
| Read/write | 32 | 12.5 | 249 | 2.54 s | 4.94 s | 6.36 s | 0 |
| Read only | 1 | 756 | 12,102 | 0.989 ms | 1.79 ms | 7.99 ms | 0 |
| Read only | 8 | 1,774 | 28,380 | 4.41 ms | 5.99 ms | 7.04 ms | 0 |
| Read only | 32 | 1,645 | 26,328 | 19.6 ms | 25.3 ms | 27.7 ms | 0 |
10 tables of 100,000 rows, loaded in 219 s. 60 to 63 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 82,350 | 74,863 | 0.407 ms | 2.62 ms | 4.45 ms |
| 1:1 set:get | 80,312 | 40,156 | 0.415 ms | 2.64 ms | 4.48 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 | 564 | 2,123 | 3,019 | 796 ms |
| Express express-postgresjs | 7,137 | 10,569 | 38,344 | 86.1 ms |
| Fastify fastify-postgres | 6,857 | 11,081 | 45,162 | 66.5 ms |
| NestJS nestjs | 5,322 | 5,639 | 22,421 | 93 ms |
| Nuxt nuxt | 6,167 | 10,325 | 35,349 | 147 ms |
| FastAPI fastapi | 3,878 | 4,905 | 19,126 | 312 ms |
| Django django-postgresql | 1,436 | 1,683 | 3,683 | 234 ms |
| Rails rails | 2,301 | 3,332 | 14,629 | 130 ms |
| Laravel laravel | 840 | 870 | 1,540 | 317 ms |
| Symfony symfony | 1,003 | 1,103 | 2,944 | 265 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 | 2.28 | 695 ms | 738 ms | 791 ms | 0% |
| Shop page | 2.28 | 946 ms | 991 ms | 1.01 s | 0% |
| Category page | 2.28 | 588 ms | 928 ms | 939 ms | 0% |
| Product page | 2.28 | 644 ms | 710 ms | 865 ms | 0% |
| Product search | 2.28 | 552 ms | 625 ms | 649 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.31 | 2.52 s | 2.81 s | 2.87 s | 0% |
| Shop page | 2.31 | 3.34 s | 3.78 s | 3.83 s | 0% |
| Category page | 2.31 | 2.96 s | 3.47 s | 3.64 s | 0% |
| Product page | 2.31 | 2.55 s | 2.74 s | 2.84 s | 0% |
| Product search | 2.31 | 2.38 s | 2.59 s | 2.67 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.44 | 741 ms | 857 ms | 893 ms | 0% |
| Cart | 4.44 | 598 ms | 688 ms | 705 ms | 0% |
| Checkout | 4.44 | 455 ms | 518 ms | 539 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.46 | 2.46 s | 3.02 s | 3.09 s | 0% |
| Cart | 4.46 | 2.55 s | 2.85 s | 2.99 s | 0% |
| Checkout | 4.46 | 2.03 s | 2.3 s | 2.37 s | 0% |
k6 with a fixed number of virtual users, 61 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 | 2.38 | 187 ms | 211 ms | 405 ms | 0% |
| Topic JSON | 1.2 | 96.3 ms | 109 ms | 121 ms | 0% |
| Home page | 1.2 | 166 ms | 192 ms | 366 ms | 0% |
| Categories page | 0.594 | 194 ms | 230 ms | 289 ms | 0% |
| User activity page | 0.594 | 113 ms | 125 ms | 146 ms | 0% |
| 4 virtual users | |||||
| Topic page | 4.33 | 411 ms | 505 ms | 736 ms | 0% |
| Topic JSON | 2.17 | 215 ms | 264 ms | 277 ms | 0% |
| Home page | 2.17 | 367 ms | 601 ms | 890 ms | 0% |
| Categories page | 1.1 | 429 ms | 621 ms | 905 ms | 0% |
| User activity page | 1.07 | 252 ms | 309 ms | 418 ms | 0% |
| 16 virtual users | |||||
| Topic page | 3.81 | 1.53 s | 1.89 s | 2.05 s | 0% |
| Topic JSON | 1.91 | 1.32 s | 1.67 s | 1.78 s | 0% |
| Home page | 1.9 | 1.48 s | 1.79 s | 1.95 s | 0% |
| Categories page | 0.932 | 1.59 s | 1.79 s | 1.85 s | 0% |
| User activity page | 0.948 | 1.32 s | 1.55 s | 1.62 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 62.1 | 50.6 ms | 140 ms | 594 ms | 0.748% |
| Topic JSON | 31.1 | 50.2 ms | 150 ms | 675 ms | 0.747% |
| Home page | 31.1 | 50 ms | 145 ms | 666 ms | 0.961% |
| Categories page | 15.6 | 48.7 ms | 143 ms | 667 ms | 1.17% |
| User activity page | 15.5 | 158 ms | 312 ms | 806 ms | 1.07% |
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,478 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 8.76 | 33.8 ms | 37.9 ms | 53.1 ms | 0% |
| Post page | 21.9 | 16.5 ms | 19.3 ms | 32.9 ms | 0% |
| Tag page | 4.38 | 22 ms | 26.1 ms | 43.5 ms | 0% |
| Author page | 4.38 | 22.7 ms | 25.3 ms | 28.9 ms | 0% |
| RSS feed | 4.38 | 27 ms | 31.4 ms | 43.8 ms | 0% |
| 4 virtual users | |||||
| Home page | 10.4 | 102 ms | 134 ms | 162 ms | 0% |
| Post page | 26.1 | 69.7 ms | 99.6 ms | 137 ms | 0% |
| Tag page | 5.24 | 59.1 ms | 91.2 ms | 114 ms | 0% |
| Author page | 5.23 | 65.5 ms | 93.2 ms | 120 ms | 0% |
| RSS feed | 5.23 | 70 ms | 94.9 ms | 126 ms | 0% |
| 16 virtual users | |||||
| Home page | 10.9 | 366 ms | 451 ms | 481 ms | 0% |
| Post page | 27.3 | 306 ms | 388 ms | 420 ms | 0% |
| Tag page | 5.46 | 196 ms | 264 ms | 292 ms | 0% |
| Author page | 5.48 | 190 ms | 257 ms | 289 ms | 0% |
| RSS feed | 5.48 | 210 ms | 289 ms | 310 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 3.78 | 31.9 ms | 43.6 ms | 55.6 ms | 0% |
| Post editor | 11.4 | 12 ms | 15.1 ms | 21.3 ms | 0% |
| Saving a draft | 11.4 | 44.1 ms | 71.4 ms | 144 ms | 0% |
| Member list | 3.78 | 37.5 ms | 44.1 ms | 57.8 ms | 0% |
| 4 virtual users | |||||
| Post list | 4.91 | 38.6 ms | 47.1 ms | 87.2 ms | 0% |
| Post editor | 14.8 | 15.3 ms | 21.9 ms | 34.8 ms | 0% |
| Saving a draft | 14.8 | 211 ms | 336 ms | 414 ms | 0% |
| Member list | 4.91 | 45.1 ms | 53 ms | 78.9 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 362 MB and MySQL at 586 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.7 | 76.9 ms | 80.2 ms | 97.7 ms | 0% |
| Blog index | 1.7 | 260 ms | 271 ms | 298 ms | 0% |
| Blog post | 5.07 | 25 ms | 38.5 ms | 40.4 ms | 0% |
| Bread page | 5.07 | 27.5 ms | 29.9 ms | 32.4 ms | 0% |
| Location page | 1.7 | 26.3 ms | 28.7 ms | 29.9 ms | 0% |
| Site search | 1.7 | 46.3 ms | 73.5 ms | 80.5 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.74 | 202 ms | 282 ms | 311 ms | 0% |
| Blog index | 2.77 | 708 ms | 889 ms | 927 ms | 0% |
| Blog post | 8.21 | 59.1 ms | 98.8 ms | 146 ms | 0% |
| Bread page | 8.23 | 63.9 ms | 92.1 ms | 103 ms | 0% |
| Location page | 2.77 | 61.1 ms | 84.7 ms | 100 ms | 0% |
| Site search | 2.74 | 89.2 ms | 181 ms | 214 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.63 | 705 ms | 911 ms | 1.02 s | 0% |
| Blog index | 2.7 | 1.83 s | 2.08 s | 2.16 s | 0% |
| Blog post | 7.91 | 396 ms | 573 ms | 677 ms | 0% |
| Bread page | 7.93 | 417 ms | 589 ms | 681 ms | 0% |
| Location page | 2.7 | 430 ms | 584 ms | 670 ms | 0% |
| Site search | 2.63 | 481 ms | 664 ms | 698 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.704 | 82.4 ms | 87.2 ms | 105 ms | 0% |
| Page explorer | 1.42 | 325 ms | 346 ms | 468 ms | 0% |
| Page editor | 2.11 | 157 ms | 261 ms | 313 ms | 0% |
| Image library | 0.704 | 60.6 ms | 66.6 ms | 582 ms | 0% |
| Admin page search | 0.704 | 33.5 ms | 71.5 ms | 73.4 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.19 | 273 ms | 464 ms | 499 ms | 0% |
| Page explorer | 2.42 | 744 ms | 1.21 s | 1.36 s | 0% |
| Page editor | 3.67 | 351 ms | 680 ms | 781 ms | 0% |
| Image library | 1.23 | 209 ms | 434 ms | 545 ms | 0% |
| Admin page search | 1.19 | 91.2 ms | 289 ms | 423 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. 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 299 MB, Postgres at 176 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 19.3 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 Xeon Processor (Icelake)
- CPU cores
- 2
- CPU frequency
- 2195 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- No
- RAM reported
- 1.9 GiB
- Swap reported
- 0 MiB
- Disk reported
- 19.3 GiB
- Virtualization reported
- KVM
- CPU steal
- 0% of busy CPU time stolen
- Distro
- Ubuntu 24.04.3 LTS
- Kernel
- 6.8.0-90-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- Yes
Advertised at test time
- Plan
- CPU-Optimized G2 2 vCPU / 2 GB
- Product line
- CPU-Optimized G2
- Location
- Manassas
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- Virtualization
- KVM
- Network
- 1 Gbps
- Transfer
- Unmetered
- Port 25
- Unknown
- Monthly price at test time
- €23.98 EUR
- Hourly price at test time
- €0.033 EUR
- YABS version
- v2026-09-20
- Ran at
- Oct 16, 2026, 03:52:26 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 16, 2026, 03:50:00 UTC
- Server created
- Oct 16, 2026, 03:50:50 UTC
- First update from the server
- Oct 16, 2026, 03:50:50 UTC
- Completed
- Oct 16, 2026, 05:48:03 UTC
- Server deleted
- Oct 16, 2026, 05:48:03 UTC
- Cost of this run
- €0.066 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.