Htop Explained

The problem with htop on Linux is that once there are 200+ processes running on the system htop takes significant portion of CPU time and utilization. This is because htop has to go through each process entry in procfs (open, read, close) every second and parse the text context instead of just calling appropriate syscall like on the OpenBSD and friends to retrieve such information. It would help if kernel provided process information in binary form instead of serializing it…

I switched to macOS from Linux two weeks ago and I am starting to regret that decision. Most — if not all — the commands that I thought I had mastered after years working on Linux environments stopped working because their BSD counterparts have slightly differences that completely break everything I try to do. It is even more frustrating when I realize that I have to deactivate security features built-in the new Apple computers in order to make things like…

Was using Prometheus for a while but have kind of fallen off the bandwagon & need to get back on! I also hear good things about Facebook's Below: > A time traveling resource monitor for modern Linux systems https://github.com/facebookincubator/below Right off the bat, in their comparison (https://github.com/facebookincubator/below/blob/main/docs/co...), they call htop a Wonderful terminal interface. Kind. But the list of limitations is severe. No view over time, no cgroup support, and very limited stats available.

Explanation of everything you can see in htop/top on Linux