Always thought top was one of those programs frozen in time since the 70s, but apparently, it has a feature set comparable to htop and the like. The default configuration just doesn't show much of it...

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 14 points 1 year ago (9 children)

Yeah, I would often just grab htop because I had no idea how to read the CPU usage out of top.
For example, for me it says:

%Cpu(s):  0,4 us,  0,4 sy,  0,0 ni, 98,8 id,  0,0 wa,  0,3 hi,  0,0 si,  0,0 st

Now that I look at it, I can guess that us and sy are supposed to be user and system time. And I guess id is supposed to be idle.
I have no guess what the other numbers might be, though. And well, I would often like to see the CPU usage per core.
Now I know that I can just press 1t and get effectively the same view as in htop.

I might learn top's filtering workflow, too. But so far, I always killed processes with ps -ef | grep <process-name> and then kill <pid>, which isn't particularly more cumbersome, so will see...

  • source
  • parent
  • hideshow 9 child comments
  • [–] 2 points 1 year ago (2 children)

    I always killed processes with ps -ef | grep and then kill

    you could check pgrep <process-name> too

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 2 points 1 year ago (1 child)

    That is a good tip. Unfortunately, I am too fish to understand it. 🙃

    I just type ps and in 9 out of 10 cases, my shell suggests ps -ef | grep <process-name>. So, it's actually less for me to type than "pgrep"...

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago*

    Far from me to try to bash a suggestion's on one's head but ^rpg or ^r<process-name> (for reverse-i-search) is probably quite fast, obviously depends entirely on your typical usage. Hard to do less than 2 keystrokes I admit.

  • source
  • parent