2 Settings I change on every htop which makes a HUGE difference.
1. I disable user threads. Those mostly just clutter up the htop view while providing no useful information.
2. I enable the process tree view. Very frequently, where a process comes from is much more important than other information. It also lets you see and track things like a compiler process which is eating through a bunch of files.
IMO, both these things should be the default behavior of htop.
For top if you use the > character it will sort by memory usage. I use that sometimes to figure out why my host is becoming laggy. Also you'll see swapd is taking up CPU.
As others mention it - it seems to shows the Watts used as well :) (and network, and GPU, and disks,....)
[0]: https://github.com/aristocratos/btop
1. I disable user threads. Those mostly just clutter up the htop view while providing no useful information.
2. I enable the process tree view. Very frequently, where a process comes from is much more important than other information. It also lets you see and track things like a compiler process which is eating through a bunch of files.
IMO, both these things should be the default behavior of htop.
I use htop often but pretty much only use it to find pid or cpu-culprits, and never really understood the rest.
You'll be glad you did.
What good does it do to stick your head in the sand?
CPUs are great for orchestrating work, GPUs are great for actually doing the work.
Get the fuck out. I do write for GPU as well. One does not replace the other.