Alternative to top, available in EPEL. Requested by user (helpscout ticket 41506) and looks useful.
A caveat is that on a busy machine the htop itself takes a non-negligible % CPU, much more than top. Hopefully users will not leave it running, but to mitigate the CPU usage in case they do, we should set a longer default delay between updates (builtin default is 1.5 seconds).
We can do this by creating /etc/htoprc:
# default 5 second delay between updates to limit CPU usage
delay=50
Users can override this with the -d command line option (values similarly given in tenths of a second) or in their personal ~/.config/htop/htoprc file (using the same syntax as in /etc/htoprc). Hopefully anyone who does either of these to shorten the delay knows what they are doing and will also be careful to run it only for a short time.
Alternative to
top
, available in EPEL. Requested by user (helpscout ticket 41506) and looks useful.A caveat is that on a busy machine the
htop
itself takes a non-negligible % CPU, much more thantop
. Hopefully users will not leave it running, but to mitigate the CPU usage in case they do, we should set a longer default delay between updates (builtin default is 1.5 seconds).We can do this by creating
/etc/htoprc
:Users can override this with the
-d
command line option (values similarly given in tenths of a second) or in their personal~/.config/htop/htoprc
file (using the same syntax as in/etc/htoprc
). Hopefully anyone who does either of these to shorten the delay knows what they are doing and will also be careful to run it only for a short time.