91–100 of 112 posts
I learned more about htop, and frankly even Linux I’m general, from this amazing in-depth explanation of what htop is displaying. https://peteris.rocks/blog/htop/
The ads are substantial, invasive (hard to follow the text) and for me were borderline NSFW. Definitely a situation for reader mode.
For those who like htop-style system monitoring tools, you should also keep these commands handy: - atop (great for finding out what's causing system-wide slowness when you're not sure whether it's CPU/disk/network/temperature/etc.) - iotop/iftop/sar (top equivalents for disk IO, network traffic, and sysstat counters) - glances/nmon/dstat/iptraf-ng (pretty monitoring CLI-GUI utils with more colors) - systemd-analyze…
- nvtop (NVIDIA GPUs htop like monitoring tool)
- radeontop (top-like GPU utilization for AMD Radeon GPUs)
There are few things more satisfying programming than firing up htop on a high core count machine and watching cpu usage light up.
Last year I ran some simulations that maxed out a 48 core machine. That was a sight to see :D
For those who like htop-style system monitoring tools, you should also keep these commands handy: - atop (great for finding out what's causing system-wide slowness when you're not sure whether it's CPU/disk/network/temperature/etc.) - iotop/iftop/sar (top equivalents for disk IO, network traffic, and sysstat counters) - glances/nmon/dstat/iptraf-ng (pretty monitoring CLI-GUI utils with more colors) - systemd-analyze…
For those who like htop-style system monitoring tools, you should also keep these commands handy: - atop (great for finding out what's causing system-wide slowness when you're not sure whether it's CPU/disk/network/temperature/etc.) - iotop/iftop/sar (top equivalents for disk IO, network traffic, and sysstat counters) - glances/nmon/dstat/iptraf-ng (pretty monitoring CLI-GUI utils with more colors) - systemd-analyze…
For those who like htop-style system monitoring tools, you should also keep these commands handy: - atop (great for finding out what's causing system-wide slowness when you're not sure whether it's CPU/disk/network/temperature/etc.) - iotop/iftop/sar (top equivalents for disk IO, network traffic, and sysstat counters) - glances/nmon/dstat/iptraf-ng (pretty monitoring CLI-GUI utils with more colors) - systemd-analyze…
For those who like htop-style system monitoring tools, you should also keep these commands handy: - atop (great for finding out what's causing system-wide slowness when you're not sure whether it's CPU/disk/network/temperature/etc.) - iotop/iftop/sar (top equivalents for disk IO, network traffic, and sysstat counters) - glances/nmon/dstat/iptraf-ng (pretty monitoring CLI-GUI utils with more colors) - systemd-analyze…
I can’t express how many times htop has made my life easy by giving me this nice interactive UX. There is a reason it’s part of every docker image I create.
> There is a reason it’s part of every docker image I create. You really shouldn't put troubleshooting tools in your container images. You can join a "toolbox" container to a running container's namespace to get your tools there when you need them. That avoids unnecessarily large images, extra build time, and extra dependencies in your image.
All of these are mandatory for containers, though... ?
htop has been on my list of applications I must install immediately on every system for at least 14 years now. I am always a bit shocked when I am reminded about how young of a project it is. I think the only younger tool that I always install is jq.
I love jq. Since I just learned this today, I'll mention that python comes with a JSON pretty-printing utility that can be used on the CLI: echo '{"some_json": "value"}' | python -m json.tool
... | python -m json.tool | python -m pygments -l json
... | python -m json.tool | pygmentize -l json
htop has been on my list of applications I must install immediately on every system for at least 14 years now. I am always a bit shocked when I am reminded about how young of a project it is. I think the only younger tool that I always install is jq.
I love jq. Since I just learned this today, I'll mention that python comes with a JSON pretty-printing utility that can be used on the CLI: echo '{"some_json": "value"}' | python -m json.tool