11–20 of 71 posts
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.
As others mention it - it seems to shows the Watts used as well :) (and network, and GPU, and disks,....)
[flagged]
You'll be glad you did.
I've relatively recently migrated over to using btop[0], and it's the kind of modern interface, useful and informative, that I needed. 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
[flagged]
Irrelevant for you does not mean irrelevant for others
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.
Earlier quoted context omitted.
Irrelevant for you does not mean irrelevant for others
Nails and hammers are great but most of us have moved on to screws and screwdrivers. 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.
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…
[flagged]