gping VS cw

gping is a souped-up version of the traditional ping utility that graphs network latency for multiple hosts as well as execution time for commands, with the option of custom colors. Our thanks for the suggestion go to fudgecakekistan.

This sounds similar to what I had in our neighborhood. Turned out there was damage on the wire up on the pole, and it started disconnecting at the break point as the wire heated up during the day and would reconnect normal as it cooled in the evening until the next day as the sun came up around 8-10am. I was able to monitor and graph the lost packets and within the terminal with https://github.com/orf/gping during the worst time period. You may go in to test at the wrong time of day and find no damaged wire but try going during the heat up time of day. Ask customers when the worst time is. I’m not a technician but a customer who happens to do IT work. I finally got a good lead tech from the cable provider to check the cable at just the right time of day and they found the break in the cable. There also was a lot of noise in the signal in general at certain frequencies. Our neighborhood now has perfect internet :D

using gping (https://github.com/orf/gping) to wifi router:

Latency Tool: gping

https://github.com/orf/gping - but probably not for 100 IPs..

For things that are commonly and almost-ideally represented as text files, there’s a lot of Rust based alternatives are faster and have more features than the old unix/GNU tools: ripgrep, fd, cw, and you can find more in this list.

Nice, beats my old Rust wc through sheer brute force on my old 12c/24t server:

A lot of unix-y tools have been rewritten in rust, where the usefulness comes from it being faster or having more features. Examples: bat, cw, lsd, ripgrep, diskonaut, gping. Maybe you could find an interesting program to rewrite?

cw, an optionally-multithreaded bytecount-accelerated wc clone

Having written a Rust wc implementation a few years ago (https://github.com/Freaky/cw), I had a look at theirs.

It's pretty naive - a simple linewise read_until loop, a conditional to avoid word splitting and such if it's not needed, and for some reason it collects results into an array and prints when it's done rather than printing as it goes.

It doesn't support --files0-from like GNU wc, so isn't a drop-in replacement from that perspective. It also has the sadly common Rust trope of only supporting filenames that are valid UTF-8.

It doesn't seem overly slow considering its simplicity - usually trading blows with GNU and BSD wc. Perhaps the most glaring omission is the lack of a fast path for -c, which should reduce to a stat() call. Also unfortunate not to use the excellent bytecount crate to provide a very fast -l/m path.

The read_until loop also makes its memory use unpredictable compared with other wc's. If you run it on /dev/zero it will try to eat your computer.