below VS iotop

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

Rewrite something like https://linux.die.net/man/1/iotop in Rust. Currently it is implemented in python, and running it as root does not give a warm fuzzy feeling.( I C version has also been made : https://github.com/Tomas-M/iotop but I have not reviewed that )

Process monitoring is mandatory but CPU and I/O monitoring can be useful. It does a moveable window so I can watch it on a second monitor, along with other app windows, when the app I'm testing is running full screen so conky, although nice, is not quite what I need. In a terminal I use htop and/or iotop but I find graphical apps to be easier to read. I didn't want to have to compile anything or use Flatpak/Snap/AppImage/whatever but there's already a bunch of monitors in the repos so I checked them out and here's what I found.

I recommend the C reimplementation of iotop btw, it has lots more features and is more efficient and is maintained. It is packaged as iotop-c in Debian and other distros.

https://github.com/Tomas-M/iotop