There's a PR in the repo that would add an additional info section to the YABS output with network details of the host machine (retrieved from https://ip-api.com/). Sample output:
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
# Yet-Another-Bench-Script #
# v2023-02-03 #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
Sun Feb 19 21:53:54 EST 2023
Basic System Information:
---------------------------------
Uptime : 46 days, 8 hours, 2 minutes
Processor : Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
CPU cores : 4 @ 2690.478 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 1.0 GiB
Swap : 0.0 KiB
Disk : 16.5 GiB
Distro : Debian GNU/Linux 9 (stretch)
Kernel : 3.16.0-1160.53.1.vz7.185.3
VM Type : OPENVZ
Basic Network Information:
---------------------------------
Protocol : IPv4
ISP : DA International Group Ltd.
ASN : AS203380 DA International Group Ltd.
Host : AlphaVPS LLC
Location : Miami, Florida (FL)
Country : United States
Question is, should this info be shown by default or should it be invoked via an option flag (-n or something). Not sure how people feel about their network info being shown in the results and if it should be default or opt-in only (via the flag). Any thoughts on this would be appreciated.
@Mason said: Question is, should this info be shown by default or should it be invoked via an option flag
bench.monster has it as default, although I never use that. If you invoke it via flag then you would need people to read about the flags. I expect about half the people will never know the flag is there. Just saying.
---------------------------------------------------------------------------
Region: Global https://bench.monster v.1.5.16 2023-01-25
Usage : curl -LsO bench.monster/speedtest.sh; bash speedtest.sh -Global
---------------------------------------------------------------------------
OS : AlmaLinux 8.7 (64 Bit)
Virt/Kernel : KVM / 4.18.0-425.13.1.el8_7.x86_64
CPU Model : AMD Ryzen 9 5950X 16-Core Processor
CPU Cores : 1 @ 3393.622 MHz x86_64 512 KB Cache
CPU Flags : AES-NI Enabled & VM-x/AMD-V Enabled
Load Average : 0.07, 0.02, 0.00
Total Space : 9.8G (4.6G ~50% used)
Total RAM : 964 MB (419 MB + 376 MB Buff in use)
Total SWAP : 511 MB (336 MB in use)
Uptime : 0 days 1:43
---------------------------------------------------------------------------
ASN & ISP : AS23470, Server24 Network by INCUBATEC GmbH - Srl Premium Hosting Service Provider
Organization : Webhosting24 Los Angeles
Location : Miami, United States / US
Region : Florida
---------------------------------------------------------------------------
Last yabs on @alwyzon EcoServer 2022 before turning it off and retiring it. It was great for the whole year and finished its mission without single issue.
Fri Feb 24 22:17:21 CET 2023
Basic System Information:
---------------------------------
Uptime : 364 days, 2 hours, 40 minutes
Processor : Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
CPU cores : 1 @ 2599.996 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 1.9 GiB
Swap : 900.0 MiB
Disk : 20.5 GiB
Distro : Slackware 15.0 x86_64
Kernel : 5.15.19
fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 59.53 MB/s (14.8k) | 664.22 MB/s (10.3k)
Write | 59.66 MB/s (14.9k) | 667.72 MB/s (10.4k)
Total | 119.19 MB/s (29.7k) | 1.33 GB/s (20.8k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 1.28 GB/s (2.5k) | 1.32 GB/s (1.2k)
Write | 1.35 GB/s (2.6k) | 1.41 GB/s (1.3k)
Total | 2.63 GB/s (5.1k) | 2.74 GB/s (2.6k)
iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Clouvider | London, UK (10G) | 895 Mbits/sec | 982 Mbits/sec | 22.0 ms
Scaleway | Paris, FR (10G) | 992 Mbits/sec | 978 Mbits/sec | 21.2 ms
NovoServe | North Holland, NL (40G) | 990 Mbits/sec | 980 Mbits/sec | 18.9 ms
Uztelecom | Tashkent, UZ (10G) | 580 Mbits/sec | 939 Mbits/sec | 75.5 ms
Clouvider | NYC, NY, US (10G) | 374 Mbits/sec | 930 Mbits/sec | 98.2 ms
Clouvider | Dallas, TX, US (10G) | 472 Mbits/sec | 914 Mbits/sec | 130 ms
Clouvider | Los Angeles, CA, US (10G) | 366 Mbits/sec | 885 Mbits/sec | 166 ms
iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Clouvider | London, UK (10G) | 988 Mbits/sec | 532 Mbits/sec | 22.2 ms
Scaleway | Paris, FR (10G) | 977 Mbits/sec | 962 Mbits/sec | 20.9 ms
NovoServe | North Holland, NL (40G) | 992 Mbits/sec | 973 Mbits/sec | 18.8 ms
Uztelecom | Tashkent, UZ (10G) | 578 Mbits/sec | 939 Mbits/sec | 75.2 ms
Clouvider | NYC, NY, US (10G) | 513 Mbits/sec | 922 Mbits/sec | 98.0 ms
Clouvider | Dallas, TX, US (10G) | 306 Mbits/sec | 892 Mbits/sec | 131 ms
Clouvider | Los Angeles, CA, US (10G) | 345 Mbits/sec | 868 Mbits/sec | 166 ms
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 532
Multi Core | 515
Full Test | https://browser.geekbench.com/v5/cpu/20739603
YABS completed in 10 min 11 sec
@emperor said:
Last yabs on @alwyzon EcoServer 2022 before turning it off and retiring it. It was great for the whole year and finished its mission without single issue.
Fri Feb 24 22:17:21 CET 2023
Basic System Information:
---------------------------------
Uptime : 364 days, 2 hours, 40 minutes
Processor : Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
CPU cores : 1 @ 2599.996 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 1.9 GiB
Swap : 900.0 MiB
Disk : 20.5 GiB
Distro : Slackware 15.0 x86_64
Kernel : 5.15.19
fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 59.53 MB/s (14.8k) | 664.22 MB/s (10.3k)
Write | 59.66 MB/s (14.9k) | 667.72 MB/s (10.4k)
Total | 119.19 MB/s (29.7k) | 1.33 GB/s (20.8k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 1.28 GB/s (2.5k) | 1.32 GB/s (1.2k)
Write | 1.35 GB/s (2.6k) | 1.41 GB/s (1.3k)
Total | 2.63 GB/s (5.1k) | 2.74 GB/s (2.6k)
iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Clouvider | London, UK (10G) | 895 Mbits/sec | 982 Mbits/sec | 22.0 ms
Scaleway | Paris, FR (10G) | 992 Mbits/sec | 978 Mbits/sec | 21.2 ms
NovoServe | North Holland, NL (40G) | 990 Mbits/sec | 980 Mbits/sec | 18.9 ms
Uztelecom | Tashkent, UZ (10G) | 580 Mbits/sec | 939 Mbits/sec | 75.5 ms
Clouvider | NYC, NY, US (10G) | 374 Mbits/sec | 930 Mbits/sec | 98.2 ms
Clouvider | Dallas, TX, US (10G) | 472 Mbits/sec | 914 Mbits/sec | 130 ms
Clouvider | Los Angeles, CA, US (10G) | 366 Mbits/sec | 885 Mbits/sec | 166 ms
iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Clouvider | London, UK (10G) | 988 Mbits/sec | 532 Mbits/sec | 22.2 ms
Scaleway | Paris, FR (10G) | 977 Mbits/sec | 962 Mbits/sec | 20.9 ms
NovoServe | North Holland, NL (40G) | 992 Mbits/sec | 973 Mbits/sec | 18.8 ms
Uztelecom | Tashkent, UZ (10G) | 578 Mbits/sec | 939 Mbits/sec | 75.2 ms
Clouvider | NYC, NY, US (10G) | 513 Mbits/sec | 922 Mbits/sec | 98.0 ms
Clouvider | Dallas, TX, US (10G) | 306 Mbits/sec | 892 Mbits/sec | 131 ms
Clouvider | Los Angeles, CA, US (10G) | 345 Mbits/sec | 868 Mbits/sec | 166 ms
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 532
Multi Core | 515
Full Test | https://browser.geekbench.com/v5/cpu/20739603
YABS completed in 10 min 11 sec
@Mason said:
Moving forward, Geekbench 6 is now the default GB test performed. Use flags to trigger GB4 and/or GB5.
Nice job, both the GB6 and the new network information segment!
But wouldn‘t it make more sense to show something like Protocol: ✔ IPv4 ✔IPv6? Could be tested by pinging an IPv4-only and an IPv6-only target once, if your current data source doesn't include this info. To me, that would seem more useful than the current Protocol: field.
@Mason said:
Moving forward, Geekbench 6 is now the default GB test performed. Use flags to trigger GB4 and/or GB5.
Nice job, both the GB6 and the new network information segment!
But wouldn‘t it make more sense to show something like Protocol: ✔ IPv4 ✔IPv6? Could be tested by pinging an IPv4-only and an IPv6-only target once, if your current data source doesn't include this info. To me, that would seem more useful than the current Protocol: field.
— Michael
Good suggestion! Definitely makes sense. I believe the person who added this piece included the Protocol IPv4 or IPv6 in the network info section so you knew which address was being used for the lookup, which also makes sense.
IPv4 and v6 connectivity are already being checked elsewhere in the script, so adding that will be simple. Will try and tweak it so it's apparent which address is being used for the lookup as well as add something showing v4/v6 status.
Comments
Unesty VPS IPv6 (€9/year)
✨🎁 Low end deals Telegram tracker: https://t.me/lowendweb
Input requested from my fellow YABSers
There's a PR in the repo that would add an additional info section to the YABS output with network details of the host machine (retrieved from https://ip-api.com/). Sample output:
Question is, should this info be shown by default or should it be invoked via an option flag (
-nor something). Not sure how people feel about their network info being shown in the results and if it should be default or opt-in only (via the flag). Any thoughts on this would be appreciated.Head Janitor @ LES • About • Rules • Support
As the new Geekbench is out now, I thought I'd do a quick GB5 vs GB6 comparison on my M1 Macbook Air:
GB5: 1734 / 7177
https://browser.geekbench.com/v5/cpu/20719550
GB6: 2310 / 7960
https://browser.geekbench.com/v6/cpu/263801
bench.monster has it as default, although I never use that. If you invoke it via flag then you would need people to read about the flags. I expect about half the people will never know the flag is there. Just saying.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Personally I'd rather this would be optional (alternatively, if enabled by default, let people hide their network info with a flag)
Contribute your idling VPS/dedi (link), Android (link) or iOS (link) devices to medical research
Spaceberg.cc - Your favorite Seedbox provider!
Last yabs on @alwyzon EcoServer 2022 before turning it off and retiring it. It was great for the whole year and finished its mission without single issue.
ServerStatus , slackvpn <-- openVPN auto install script for Slackware 15
You turn your idle boxes off?
Free NAT KVM | Free NAT LXC | Bobr
ITS WEDNESDAY MY DUDES
That one was the only in few which weren't idling
ServerStatus , slackvpn <-- openVPN auto install script for Slackware 15
Spaceberg.cc - Your favorite Seedbox provider!
Hosthatch APAC 1TB storage
I bench YABS 24/7/365 unless it's a leap year.
GreenCloud Budget KVM DE-2 (25$/year)
✨🎁 Low end deals Telegram tracker: https://t.me/lowendweb
Alwyzon Storage Server 1T | 7.61(with Taxes) EUR/m | with FDE
AlphaVPS 512GB Storage | 3.5 EUR/m | with FDE
Fastpipe (combahton) SE-2 | 3.99 EUR/m
server-factory.com 4 cores (Ryzen 5950X), 16 GB RAM, 200 GB NVME storage, 32TB@1Gbps for 17 euros per month (location The Netherlands)
Lead Platform Architect at the day job, Ethical Hacker/Bug Bounty Hunter on the side
MadCityServers $7/m Chicago
Hetzner EX43
Amadex • Hosting Forums • Wie ist meine IP-Adresse? • AS215325
Forum for System Administrators: sysadminforum.com
Moving forward, Geekbench 6 is now the default GB test performed. Use flags to trigger GB4 and/or GB5.
Head Janitor @ LES • About • Rules • Support
Let me test the GB 6 on my babies
Amadex • Hosting Forums • Wie ist meine IP-Adresse? • AS215325
Forum for System Administrators: sysadminforum.com
greencloud $20/3m EPYCDE-3, DE
greencloud 10GbpsNLPromo-2 $60/year
Nice job, both the GB6 and the new network information segment!
But wouldn‘t it make more sense to show something like
Protocol: ✔ IPv4 ✔IPv6? Could be tested by pinging an IPv4-only and an IPv6-only target once, if your current data source doesn't include this info. To me, that would seem more useful than the currentProtocol:field.— Michael
Alwyzon - Virtual Servers in Austria starting at 4,49 €/month (excl. VAT)
Oh, and to stay on-topic, here is a YABS.
Alwyzon - Virtual Servers in Austria starting at 4,49 €/month (excl. VAT)
Good suggestion! Definitely makes sense. I believe the person who added this piece included the Protocol IPv4 or IPv6 in the network info section so you knew which address was being used for the lookup, which also makes sense.
IPv4 and v6 connectivity are already being checked elsewhere in the script, so adding that will be simple. Will try and tweak it so it's apparent which address is being used for the lookup as well as add something showing v4/v6 status.
Head Janitor @ LES • About • Rules • Support
Spaceberg.cc - Your favorite Seedbox provider!
Greencloud 9999 Epyc Kansas, to test GB6