below VS bottom

below is good. Enable the service and add the --dict-compress-chunk-size argument, and you can keep a week of... pretty much everything, by cgroup and by process, at 5 second sampling period, in under 1 GB of /var/log space.

IO wait is counted against load by linux. So high IO pressure, i.e. found in `/proc/pressure`

I'm liking this project https://github.com/facebookincubator/below

It's packaged in Fedora.

I created something similar for our project “below” (https://github.com/facebookincubator/below/blob/main/below/b...).

The program collects system resource metrics into a data structure and we need to display the fields with different styles and formats. In order to decouple the data structure from rendering, Queriable (Keyable) and FieldId (combine KeyPath + mirror struct into enum) are used. I will definitely like to checkout the KeyPath implementation as it seems more general.

System Monitors: Would include Below.

I have been using glances for a terminal sysmon but I don't like that it eats so much RAM. Can someone please recommend a system monitor that is easy to comprehend and less resource hungry?

I am also curious about below [0] since it came up recently.

[0] https://github.com/facebookincubator/below

Below! https://github.com/facebookincubator/below

bottom

I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom

It works on Windows also.

If anyone is looking for a "top" like, written in Rust, might have a look at https://github.com/ClementTsang/bottom

Looks like bottom with another theme

bottom - A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.