Google Cloud (asia-south2) (Google Compute Engine) - n2-4c16g-delhi Yab
August 22nd 2023
This is the yab (yabs.sh results) for tests that were run on a Google Cloud (asia-south2) (Google Compute Engine) server on August 22nd 2023.
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 (asia-south2) (Google Compute Engine) |
|---|---|
| VPS Plan | n2-4c16g-delhi |
| OS Version | Ubuntu 22.04.2 LTS |
| Data Center Location | New Delhi, Delhi, India |
Specs
| Processor | Intel(R) Xeon(R) CPU @ 2.80GHz |
|---|---|
| CPU cores | 4 @ 2800.354 MHz |
| RAM | 15.6 GiB |
| Disk | 10.1 GB |
| Swap | 0.0 B |
| Kernel | 5.19.0-1030-gcp |
| AES-NI | ✔ Enabled |
| VM-x/AMD-V | ❌ Disabled |
| VM Type |
Raw Yabs.sh Output
{
"version": "v2023-04-23",
"time": "20230822-165938",
"os": {
"arch": "x64",
"distro": "Ubuntu 22.04.2 LTS",
"kernel": "5.19.0-1030-gcp",
"uptime": 739.6,
"vm": "KVM"
},
"net": {
"ipv4": true,
"ipv6": false
},
"cpu": {
"model": "Intel(R) Xeon(R) CPU @ 2.80GHz",
"cores": 4,
"freq": "2800.354 MHz",
"aes": true,
"virt": false
},
"mem": {
"ram": 16369472,
"ram_units": "KiB",
"swap": 0,
"swap_units": "KiB",
"disk": 10080946,
"disk_units": "KB"
},
"ip_info": {
"protocol": "IPv4",
"isp": "Google LLC",
"asn": "AS15169 Google LLC",
"org": "Google Cloud (asia-south2)",
"city": "New Delhi",
"region": "Delhi",
"region_code": "DL",
"country": "India"
},
"fio": [
{
"bs": "4k",
"speed_r": 6472,
"iops_r": 1618,
"speed_w": 6475,
"iops_w": 1618,
"speed_rw": 12947,
"iops_rw": 3236,
"speed_units": "KBps"
},
{
"bs": "64k",
"speed_r": 99252,
"iops_r": 1550,
"speed_w": 99774,
"iops_w": 1558,
"speed_rw": 199026,
"iops_rw": 3108,
"speed_units": "KBps"
},
{
"bs": "512k",
"speed_r": 140163,
"iops_r": 273,
"speed_w": 147610,
"iops_w": 288,
"speed_rw": 287773,
"iops_rw": 561,
"speed_units": "KBps"
},
{
"bs": "1m",
"speed_r": 138395,
"iops_r": 135,
"speed_w": 147612,
"iops_w": 144,
"speed_rw": 286007,
"iops_rw": 279,
"speed_units": "KBps"
}
],
"iperf": [
{
"mode": "IPv4",
"provider": "Clouvider",
"loc": "London, UK (10G)",
"send": "13.9 Mbits/sec",
"recv": "18.6 Mbits/sec",
"latency": "264 ms"
},
{
"mode": "IPv4",
"provider": "Scaleway",
"loc": "Paris, FR (10G)",
"send": "683 Mbits/sec",
"recv": "614 Mbits/sec",
"latency": "269 ms"
},
{
"mode": "IPv4",
"provider": "NovoServe",
"loc": "North Holland, NL (40G)",
"send": "585 Mbits/sec",
"recv": "busy ",
"latency": "264 ms"
},
{
"mode": "IPv4",
"provider": "Uztelecom",
"loc": "Tashkent, UZ (10G)",
"send": "busy ",
"recv": "busy ",
"latency": "849 ms"
},
{
"mode": "IPv4",
"provider": "Clouvider",
"loc": "NYC, NY, US (10G)",
"send": "busy ",
"recv": "busy ",
"latency": "267 ms"
},
{
"mode": "IPv4",
"provider": "Clouvider",
"loc": "Dallas, TX, US (10G)",
"send": "busy ",
"recv": "18.7 Mbits/sec",
"latency": "279 ms"
},
{
"mode": "IPv4",
"provider": "Clouvider",
"loc": "Los Angeles, CA, US (10G)",
"send": "15.4 Mbits/sec",
"recv": "23.6 Mbits/sec",
"latency": "240 ms"
}
],
"geekbench": [
{
"version": 6,
"single": 1167,
"multi": 2559,
"url": "https://browser.geekbench.com/v6/cpu/2352435"
}
],
"runtime": {
"start": 1692723578,
"end": 1692724374,
"elapsed": 796
}
}
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/2352435 |
|---|---|
| Multi Core | 2559 |
| Single Core | 1167 |
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 | 6.5 MB/s 1.618k IOPS | 99.3 MB/s 1.55k IOPS | 140.2 MB/s 0.273k IOPS | 138.4 MB/s 0.135k IOPS |
| Write | 6.5 MB/s 1.618k IOPS | 99.8 MB/s 1.558k IOPS | 147.6 MB/s 0.288k IOPS | 147.6 MB/s 0.144k IOPS |
| Total | 12.9 MB/s 3.236k IOPS | 199.0 MB/s 3.108k IOPS | 287.8 MB/s 0.561k IOPS | 286.0 MB/s 0.279k IOPS |
Iperf3 ipv4
Iperf3 tests download and upload speeds to various locations using 8 parallel threads.
| Download | Upload | |
|---|---|---|
|
Scaleway Paris, FR (10G) |
614 Mbits/sec | 683 Mbits/sec |
|
Clouvider London, UK (10G) |
19 Mbits/sec | 14 Mbits/sec |
|
Clouvider NYC, NY, US (10G) |
busy | busy |
|
Uztelecom Tashkent, UZ (10G) |
busy | busy |
|
Clouvider Dallas, TX, US (10G) |
19 Mbits/sec | busy |
|
NovoServe North Holland, NL (40G) |
busy | 585 Mbits/sec |
|
Clouvider Los Angeles, CA, US (10G) |
24 Mbits/sec | 15 Mbits/sec |