Benchy - Benchmark with color !

lewellyn

If OpenBSD is still using their fork of the ancient pdksh, that's probably why. That shell is filled with bugs, honestly, and why mksh is even a thing (it was a fork to fix pdksh originally).

On the plus side, many distros have a pdksh available, so it should be replicable on e.g. Debian/Ubuntu via apt-get install pdksh.

Arkas

I like the colors!

Ganonk

Liso

@ailice said:

@lewellyn said:

@ailice will probably need to provide more information to ensure that it's made to work for them. Like which OpenBSD version and which architecture.

Its OpenBSD 7.2 amd64, AFAIK sh was symlink with ksh on OpenBSD. I also have ksh on Alpine but script running fine.
This probably some OpenBSD stuff

BSD use a whole lot different architecture than Linux Based System, the binary compiled in Linux cannot guaranteed to work in BSD. A simple workaround would be install the dependencies first before running benchy: pkg_add iperf3 fio

Below is sample from my bsd setup, color works fine.

liso$ benchy -kgd
# # # # # # # # # # # # # # # # # # # # #
#             Benchy v2.4               #
#    https://github.com/L1so/benchy     #
# # # # # # # # # # # # # # # # # # # # #
#        02 Dec 2022 23:02 WIB          #
# # # # # # # # # # # # # # # # # # # # #

Server Insight                                  Hardware Information
---------------------                           ---------------------
OS         : OpenBSD 7.2                        Model       : AMD EPYC 7702P 64-Core Processor
Location   : Singapore                          Core        : 1 @ 2000 Mhz
Kernel     : GENERIC#728                        AES-NI      : ✔ Enabled
Uptime     : 12 hrs 4 mins                      VM-x/AMD-V  : ✔ Enabled
Virt       : none                               Swap        : 2.4 GiB   

Disk & Memory Usage                             Network Information
---------------------                           ---------------------
Disk       : 985.8 MiB                          ASN         : AS399686  
Disk Usage : 349.0 MiB (37% Used)               ISP         : SEMIBAND  
Mem        : 1.0 GiB                            IPv4        : ✔ Enabled
Mem Usage  : 13.0 MiB (1% Used)                 IPv6        : ❌ Disabled

Network Performance Test (Region: Mixed)
+---------------------------------------------------------------------------------+
| Prot. | Provider    | Location        | Send         | Receive      | Latency   |
+---------------------------------------------------------------------------------+
| IPv4  | Airstream   | Wisconsin, US   |  125.7 Mb/s  |   73.4 Mb/s  |  194.3 ms |
|       | Uztelecom   | Tashkent, UZ    |        busy  |        busy  |  193.9 ms |
|       | Novogara    | Amsterdam, NL   |  123.6 Mb/s  |   91.4 Mb/s  |  154.0 ms |
|       | FiberBy     | Copenhagen, DK  |  173.6 Mb/s  |        busy  |  178.2 ms |
+---------------------------------------------------------------------------------+

Two things to note:

• Disk Benchmark only works in root, I run above test with non-root user.
• Geekbench5 does not work at all.

Liso

You can now specify which disk to be benched by adding --disk=ARG option. Tested on 4x25 GB VM.

• --disk=all will bench all available disk on the system (example output: https://bin.gy/hersisenel)
• --disk=/dev/vdd,/dev/vdc will bench both /dev/vdd and /dev/vdc, you can replace the value with other drive that you have write access to (example output: https://bin.gy/sangaletia).

Following snippet is will produce equivalent result. When in doubt, use double quoting around your drive name-- the argument must be separated with comma.

• --disk=all
• -f "all" or -f all
• --disk "all" or --disk all