Google Cloud (us-east4) (Google Compute Engine) - Kaggle Yab
May 18th 2026
This is the yab (yabs.sh results) for tests that were run on a Google Cloud (us-east4) (Google Compute Engine) server on May 18th 2026.
yabs.sh is an easy to run and powerful script that runs a full set of benchmarks on your server. Get Started with Yabs. You can collect, organize and visualize your yabs for free at VPSBenchmarks.
Go to your Dashboard to manage your yabs.
Compare Geekbench, Fio and Iperf3 benchmark results from the Yabs comparison page.
Server
| Provider | Google Cloud (us-east4) (Google Compute Engine) |
|---|---|
| VPS Plan | Kaggle |
| OS Version | Ubuntu 22.04.5 LTS |
| Data Center Location | Washington, Washington, D.C., United States |
Specs
| Processor | Intel(R) Xeon(R) CPU @ 2.20GHz |
|---|---|
| CPU cores | 4 @ 2199.998 MHz |
| RAM | 31.4 GiB |
| Disk | 8.5 TB |
| Swap | 0.0 B |
| Kernel | 6.6.122+ |
| AES-NI | ✔ Enabled |
| VM-x/AMD-V | ❌ Disabled |
| VM Type |
Raw Yabs.sh Output
{
"version": "v2026-05-11",
"time": "20260518-131333",
"os": {
"arch": "x64",
"distro": "Ubuntu 22.04.5 LTS",
"kernel": "6.6.122+",
"uptime": 243.89,
"vm": "DOCKER"
},
"net": {
"ipv4": true,
"ipv6": false
},
"cpu": {
"model": "Intel(R) Xeon(R) CPU @ 2.20GHz",
"cores": 4,
"freq": "2199.998 MHz",
"aes": true,
"virt": false
},
"mem": {
"ram": 32873504,
"ram_units": "KiB",
"swap": 0,
"swap_units": "KiB",
"disk": 8474492404,
"disk_units": "KB"
},
"ip_info": {
"protocol": "IPv4",
"isp": "Google LLC",
"asn": "AS396982 Google LLC",
"org": "Google Cloud (us-east4)",
"city": "Washington",
"region": "Washington, D.C.",
"region_code": "DC",
"country": "United States"
},
"partition": "/dev/loop1",
"fio": [
{
"bs": "4k",
"speed_r": null,
"iops_r": null,
"speed_w": null,
"iops_w": null,
"speed_rw": 0,
"iops_rw": 0,
"speed_units": "KBps"
},
{
"bs": "64k",
"speed_r": null,
"iops_r": null,
"speed_w": null,
"iops_w": null,
"speed_rw": 0,
"iops_rw": 0,
"speed_units": "KBps"
},
{
"bs": "512k",
"speed_r": null,
"iops_r": null,
"speed_w": null,
"iops_w": null,
"speed_rw": 0,
"iops_rw": 0,
"speed_units": "KBps"
},
{
"bs": "1m",
"speed_r": null,
"iops_r": null,
"speed_w": null,
"iops_w": null,
"speed_rw": 0,
"iops_rw": 0,
"speed_units": "KBps"
}
],
"iperf": [
{
"mode": "IPv4",
"provider": "Clouvider",
"loc": "London, UK (10G)",
"send": "2.32 Gbits/sec",
"recv": "2.99 Gbits/sec",
"latency": "--"
},
{
"mode": "IPv4",
"provider": "Eranium",
"loc": "Amsterdam, NL (100G)",
"send": "1.87 Gbits/sec",
"recv": "2.81 Gbits/sec",
"latency": "--"
},
{
"mode": "IPv4",
"provider": "Uztelecom",
"loc": "Tashkent, UZ (10G)",
"send": "busy ",
"recv": "1.13 Gbits/sec",
"latency": "--"
},
{
"mode": "IPv4",
"provider": "Leaseweb",
"loc": "Singapore, SG (10G)",
"send": "683 Mbits/sec",
"recv": "909 Mbits/sec",
"latency": "--"
},
{
"mode": "IPv4",
"provider": "Clouvider",
"loc": "Los Angeles, CA, US (10G)",
"send": "2.49 Gbits/sec",
"recv": "2.90 Gbits/sec",
"latency": "--"
},
{
"mode": "IPv4",
"provider": "Leaseweb",
"loc": "NYC, NY, US (10G)",
"send": "4.00 Gbits/sec",
"recv": "5.13 Gbits/sec",
"latency": "--"
},
{
"mode": "IPv4",
"provider": "Edgoo",
"loc": "Sao Paulo, BR (1G)",
"send": "906 Mbits/sec",
"recv": "1.39 Gbits/sec",
"latency": "--"
}
],
"geekbench": [
{
"version": 6,
"single": null,
"multi": null,
"url": "https://browser.geekbench.com/v6/cpu/18039458"
}
],
"runtime": {
"start": 1779110013,
"end": 1779110854,
"elapsed": 841
}
}
Results Summary
The scale in the charts between 0 and 100 represents the performance of this server for each metric relative to the performance of all other servers tested recently at VPSBenchmarks for that same metric.
- 100 means the server is the fastest for this metric.
- 50 means the server has exactly median performance for this metric.
- 0 means the server is the slowest for this metric.
Geekbench 6
Geekbench measures your processor's single-core and multi-core power.
| Full Test | https://browser.geekbench.com/v6/cpu/18039458 |
|---|---|
| Multi Core | 1687 |
| Single Core | 786 |
Fio
This Fio test evaluates disk performance in 4 random read and write runs with different block sizes, 50% reads and 50% writes.
All fio tests below run in asynchronous direct mode using libaio and use 2 execution threads regardless of the size of the server.
| 4k | 64k | 512k | 1m | |
|---|---|---|---|---|
| Read | 0 MB/s 0k IOPS | 0 MB/s 0k IOPS | 0 MB/s 0k IOPS | 0 MB/s 0k IOPS |
| Write | 0 MB/s 0k IOPS | 0 MB/s 0k IOPS | 0 MB/s 0k IOPS | 0 MB/s 0k IOPS |
| Total | 0 MB/s 0k IOPS | 0 MB/s 0k IOPS | 0 MB/s 0k IOPS | 0 MB/s 0k IOPS |
Iperf3 ipv4
Iperf3 tests download and upload speeds to various locations using 8 parallel threads.
| Download | Upload | |
|---|---|---|
|
Edgoo Sao Paulo, BR (1G) |
1423 Mbits/sec | 906 Mbits/sec |
|
Clouvider London, UK (10G) |
3062 Mbits/sec | 2376 Mbits/sec |
|
Leaseweb NYC, NY, US (10G) |
5253 Mbits/sec | 4096 Mbits/sec |
|
Eranium Amsterdam, NL (100G) |
2877 Mbits/sec | 1915 Mbits/sec |
|
Leaseweb Singapore, SG (10G) |
909 Mbits/sec | 683 Mbits/sec |
|
Uztelecom Tashkent, UZ (10G) |
1157 Mbits/sec | busy |
|
Clouvider Los Angeles, CA, US (10G) |
2970 Mbits/sec | 2550 Mbits/sec |