Gcore CPU-Optimized G1 2 vCPU / 2 GB
Manassas
Server
-
ProviderGcore
-
PlanCPU-Optimized G1 2 vCPU / 2 GB
-
LocationManassas
-
vCPU2
-
RAM2 GB
-
Storage
-
Network1 Gbps
-
OS imageubuntu-24.04
-
TriggerScheduled
-
Queued atOct 15, 2026, 09:39:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 937 | 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 |
923
|
Single-core only |
| Navigation |
1,161
|
Single-core only |
| HTML5 Browser |
934
|
Single-core only |
| PDF Viewer |
980
|
Single-core only |
| Photo Library |
751
|
Single-core only |
| Clang |
950
|
Single-core only |
| Text Processing |
933
|
Single-core only |
| Asset Compression |
1,032
|
Single-core only |
| HDR |
833
|
Single-core only |
| Photo Editor |
961
|
Single-core only |
| Ray Tracer |
924
|
Single-core only |
| Structure from Motion |
1,031
|
Single-core only |
| Game Physics |
890
|
Single-core only |
| Video Encoder |
883
|
Single-core only |
| Audio Encoder |
972
|
Single-core only |
| Video Player |
894
|
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 | 19.4 GB/s | 3 | 0.465% |
| Scale higher is better | 19.3 GB/s | 3 | 0.424% |
| Add higher is better | 21.5 GB/s | 3 | 0.356% |
| Triad higher is better | 21.5 GB/s | 3 | 0.409% |
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 | 378/s | 3 | 3.13% |
| RSA 4096 verifies higher is better | 25,612/s | 3 | 1.11% |
| SHA-256 higher is better | 460 MB/s | 3 | 2.35% |
| AES-256-GCM higher is better | 6.02 GB/s | 3 | 2.39% |
| ChaCha20-Poly1305 higher is better | 4.02 GB/s | 3 | 1.56% |
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.57 ms | 3 | 0% |
| Requests per second, 90th percentile higher is better | 432/s | 3 | 0.134% |
| Request latency, 99.9th percentile lower is better | 9.61 ms | 3 | 5% |
| Requests per second, average higher is better | 423/s | 3 | 0.0868% |
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 (597 IOPS) | 2.4 MB/s (603 IOPS) | 4.7 MB/s (1,200 IOPS) |
| 64K | 37.5 MB/s (599 IOPS) | 37.8 MB/s (604 IOPS) | 75.2 MB/s (1,203 IOPS) |
| 512K | 48.8 MB/s (97 IOPS) | 51.5 MB/s (103 IOPS) | 100.3 MB/s (200 IOPS) |
| 1M | 48.3 MB/s (48 IOPS) | 51.3 MB/s (51 IOPS) | 99.6 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.37 Gbps | 1.25 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.41 Gbps | 1.36 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 737 Mbps | 955 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.4 Gbps | 1.34 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.5 Gbps | 1.44 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 | 437 | 2.29 ms |
| fdatasync | 386 | 2.59 ms |
| fsync | 106 | 9.44 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 100 | 9.98 ms |
| Two 8 kB writes | ||
| open_datasync | 166 | 6.04 ms |
| fdatasync | 347 | 2.89 ms |
| fsync | 125 | 7.99 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 58.3 | 17.2 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 116 | 8.61 ms |
| 2 * 8kB open_sync writes | 53.2 | 18.8 ms |
| 4 * 4kB open_sync writes | 29.2 | 34.3 ms |
| 8 * 2kB open_sync writes | 14.5 | 68.7 ms |
| 16 * 1kB open_sync writes | 7.56 | 132 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 108 | 9.3 ms |
| write, close, fsync | 113 | 8.83 ms |
| Non-synced 8 kB writes | ||
| write | 613,181 | 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 | 245 | 3.44 ms | 7.05 ms | 11.7 ms | 251 ms | 0 |
| Read/write (TPC-B like) | 8 | 930 | 6.43 ms | 19.7 ms | 38 ms | 92.5 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,239 | 15.4 ms | 77.1 ms | 152 ms | 263 ms | 0 |
| Read only | 1 | 20,729 | 0.045 ms | 0.067 ms | 0.091 ms | 0.177 ms | 0 |
| Read only | 8 | 35,922 | 0.201 ms | 0.329 ms | 0.414 ms | 1.67 ms | 0 |
| Read only | 32 | 35,517 | 0.778 ms | 1.23 ms | 1.75 ms | 3.11 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 4.14 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 | 166 | 4.8 ms | 10.6 ms | 23.3 ms | 46.3 ms | 0 |
| Read/write (TPC-B like) | 8 | 388 | 10.5 ms | 87.5 ms | 133 ms | 288 ms | 0 |
| Read/write (TPC-B like) | 32 | 356 | 74.2 ms | 218 ms | 310 ms | 614 ms | 0 |
| Read only | 1 | 606 | 1.03 ms | 4.32 ms | 7.66 ms | 52.4 ms | 0 |
| Read only | 8 | 823 | 7.96 ms | 21.8 ms | 32.4 ms | 105 ms | 0 |
| Read only | 32 | 301 | 32.5 ms | 561 ms | 933 ms | 1.27 s | 0 |
Scale 100 (10,000,000 accounts), loaded in 86.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 | 4.53 | 90.6 | 109 ms | 646 ms | 1.13 s | 0 |
| Read/write | 8 | 6.15 | 123 | 1.01 s | 3.45 s | 4.13 s | 0 |
| Read/write | 32 | 12.3 | 247 | 2.59 s | 5.31 s | 6.14 s | 0 |
| Read only | 1 | 613 | 9,812 | 1.32 ms | 2.62 ms | 7.3 ms | 0 |
| Read only | 8 | 1,200 | 19,207 | 6.43 ms | 9.06 ms | 10.8 ms | 0 |
| Read only | 32 | 1,188 | 19,002 | 26.7 ms | 33.7 ms | 38.2 ms | 0 |
10 tables of 100,000 rows, loaded in 217 s. 60 to 64 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 54,050 | 49,136 | 0.895 ms | 3.04 ms | 4.77 ms |
| 1:1 set:get | 53,005 | 26,502 | 0.935 ms | 3.07 ms | 4.83 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 | 406 | 1,531 | 2,015 | 1.24 s |
| Express express-postgresjs | 6,018 | 8,003 | 25,565 | 78.9 ms |
| Fastify fastify-postgres | 5,806 | 9,009 | 28,566 | 77.8 ms |
| NestJS nestjs | 3,554 | 3,927 | 14,131 | 121 ms |
| Nuxt nuxt | 5,130 | 8,062 | 23,876 | 108 ms |
| FastAPI fastapi | 2,713 | 3,411 | 14,494 | 340 ms |
| Django django-postgresql | 1,121 | 1,258 | 2,522 | 304 ms |
| Rails rails | 1,587 | 2,212 | 8,693 | 208 ms |
| Laravel laravel | 586 | 626 | 1,142 | 482 ms |
| Symfony symfony | 747 | 813 | 2,129 | 393 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.65 | 937 ms | 1.06 s | 1.13 s | 0% |
| Shop page | 1.65 | 1.28 s | 1.39 s | 1.49 s | 0% |
| Category page | 1.65 | 811 ms | 1.29 s | 1.36 s | 0% |
| Product page | 1.65 | 876 ms | 983 ms | 1.06 s | 0% |
| Product search | 1.65 | 744 ms | 882 ms | 913 ms | 0% |
| 32 virtual users | |||||
| Home page | 1.81 | 3.46 s | 3.86 s | 4.03 s | 0% |
| Shop page | 1.81 | 4.6 s | 5.13 s | 5.22 s | 0% |
| Category page | 1.76 | 4.1 s | 4.8 s | 5.12 s | 0% |
| Product page | 1.42 | 3.52 s | 3.72 s | 3.88 s | 0% |
| Product search | 1.35 | 3.22 s | 3.44 s | 3.5 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 3.15 | 1.01 s | 1.14 s | 1.17 s | 0% |
| Cart | 3.15 | 827 ms | 933 ms | 948 ms | 0% |
| Checkout | 3.15 | 621 ms | 729 ms | 759 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 3.23 | 3.4 s | 4.08 s | 4.26 s | 0% |
| Cart | 3.23 | 3.56 s | 3.88 s | 4.08 s | 0% |
| Checkout | 3.23 | 2.79 s | 3.13 s | 3.23 s | 0% |
k6 with a fixed number of virtual users, 63 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.46 | 311 ms | 356 ms | 535 ms | 0% |
| Topic JSON | 0.74 | 151 ms | 178 ms | 234 ms | 0% |
| Home page | 0.74 | 267 ms | 333 ms | 568 ms | 0% |
| Categories page | 0.362 | 319 ms | 343 ms | 351 ms | 0% |
| User activity page | 0.362 | 187 ms | 209 ms | 380 ms | 0% |
| 4 virtual users | |||||
| Topic page | 2.83 | 609 ms | 851 ms | 1.19 s | 0% |
| Topic JSON | 1.42 | 324 ms | 412 ms | 431 ms | 0% |
| Home page | 1.41 | 555 ms | 896 ms | 1.27 s | 0% |
| Categories page | 0.737 | 628 ms | 785 ms | 1.11 s | 0% |
| User activity page | 0.704 | 372 ms | 638 ms | 821 ms | 0% |
| 16 virtual users | |||||
| Topic page | 2.81 | 1.65 s | 2.21 s | 2.68 s | 0% |
| Topic JSON | 1.39 | 1.35 s | 1.72 s | 1.91 s | 0% |
| Home page | 1.39 | 1.63 s | 2 s | 2.38 s | 0% |
| Categories page | 0.703 | 1.65 s | 1.89 s | 1.97 s | 0% |
| User activity page | 0.719 | 1.46 s | 1.72 s | 1.94 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 57 | 79.8 ms | 185 ms | 235 ms | 0% |
| Topic JSON | 28.5 | 79 ms | 188 ms | 246 ms | 0% |
| Home page | 28.5 | 82.6 ms | 185 ms | 236 ms | 0% |
| Categories page | 14.3 | 78.5 ms | 187 ms | 308 ms | 0% |
| User activity page | 14.3 | 248 ms | 400 ms | 562 ms | 0% |
k6 with a fixed number of virtual users, 60 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 362 MB of it. The container peaked at 1,504 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 5.7 | 48.3 ms | 61.5 ms | 96.5 ms | 0% |
| Post page | 14.2 | 26 ms | 33.8 ms | 48.5 ms | 0% |
| Tag page | 2.85 | 33.6 ms | 40.8 ms | 48.4 ms | 0% |
| Author page | 2.85 | 33.4 ms | 42.2 ms | 61.3 ms | 0% |
| RSS feed | 2.83 | 41.7 ms | 52.4 ms | 60.7 ms | 0% |
| 4 virtual users | |||||
| Home page | 6.97 | 149 ms | 221 ms | 250 ms | 0% |
| Post page | 17.4 | 102 ms | 151 ms | 195 ms | 0% |
| Tag page | 3.51 | 94.1 ms | 143 ms | 174 ms | 0% |
| Author page | 3.48 | 97.4 ms | 143 ms | 184 ms | 0% |
| RSS feed | 3.46 | 109 ms | 151 ms | 209 ms | 0% |
| 16 virtual users | |||||
| Home page | 7.1 | 566 ms | 684 ms | 742 ms | 0% |
| Post page | 17.7 | 475 ms | 603 ms | 664 ms | 0% |
| Tag page | 3.55 | 299 ms | 406 ms | 454 ms | 0% |
| Author page | 3.53 | 306 ms | 419 ms | 447 ms | 0% |
| RSS feed | 3.51 | 310 ms | 416 ms | 468 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 2.53 | 51.6 ms | 64.5 ms | 86.3 ms | 0% |
| Post editor | 7.63 | 19 ms | 26.4 ms | 36 ms | 0% |
| Saving a draft | 7.61 | 64.5 ms | 95.1 ms | 169 ms | 0% |
| Member list | 2.53 | 59.5 ms | 72.2 ms | 84.1 ms | 0% |
| 4 virtual users | |||||
| Post list | 3.21 | 58.9 ms | 79.1 ms | 134 ms | 0% |
| Post editor | 9.68 | 23.2 ms | 36.8 ms | 62.8 ms | 0% |
| Saving a draft | 9.72 | 313 ms | 470 ms | 600 ms | 0% |
| Member list | 3.22 | 65.7 ms | 86.9 ms | 109 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 346 MB and MySQL at 582 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.1 | 117 ms | 137 ms | 147 ms | 0% |
| Blog index | 1.1 | 413 ms | 451 ms | 461 ms | 0% |
| Blog post | 3.25 | 38.8 ms | 56.2 ms | 65.8 ms | 0% |
| Bread page | 3.27 | 43.6 ms | 52 ms | 58.9 ms | 0% |
| Location page | 1.1 | 39.9 ms | 49.5 ms | 53.1 ms | 0% |
| Site search | 1.08 | 76.2 ms | 121 ms | 131 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.02 | 284 ms | 375 ms | 453 ms | 0% |
| Blog index | 2.05 | 971 ms | 1.25 s | 1.35 s | 0% |
| Blog post | 6.06 | 77.9 ms | 129 ms | 169 ms | 0% |
| Bread page | 6.09 | 84.4 ms | 123 ms | 147 ms | 0% |
| Location page | 2.07 | 79.2 ms | 123 ms | 142 ms | 0% |
| Site search | 2 | 130 ms | 251 ms | 336 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.02 | 948 ms | 1.32 s | 1.5 s | 0% |
| Blog index | 2 | 2.46 s | 2.85 s | 2.98 s | 0% |
| Blog post | 5.95 | 528 ms | 913 ms | 1.04 s | 0% |
| Bread page | 5.98 | 513 ms | 847 ms | 1.08 s | 0% |
| Location page | 1.97 | 515 ms | 886 ms | 1 s | 0% |
| Site search | 1.99 | 619 ms | 1.01 s | 1.25 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.458 | 131 ms | 154 ms | 166 ms | 0% |
| Page explorer | 0.949 | 473 ms | 557 ms | 659 ms | 0% |
| Page editor | 1.41 | 238 ms | 345 ms | 475 ms | 0% |
| Image library | 0.458 | 89.9 ms | 105 ms | 1.01 s | 0% |
| Admin page search | 0.458 | 52.9 ms | 107 ms | 109 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.762 | 328 ms | 637 ms | 718 ms | 0% |
| Page explorer | 1.59 | 1.14 s | 2.06 s | 2.19 s | 0% |
| Page editor | 2.37 | 559 ms | 1.02 s | 1.06 s | 0% |
| Image library | 0.778 | 302 ms | 638 ms | 671 ms | 0% |
| Admin page search | 0.762 | 117 ms | 300 ms | 366 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 295 MB, Postgres at 176 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0.1% 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 (Skylake, IBRS)
- 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.1% 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 G1 2 vCPU / 2 GB
- Product line
- CPU-Optimized G1
- 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 15, 2026, 10:13:26 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 15, 2026, 09:39:00 UTC
- First update from the server
- Oct 15, 2026, 10:12:58 UTC
- Completed
- Oct 15, 2026, 12:14:00 UTC
- Server deleted
- Oct 15, 2026, 12:14:00 UTC
- Cost of this run
- €0.068 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.