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…
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…
Yeah, I would often just grab
htopbecause I had no idea how to read the CPU usage out oftop.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 stNow that I look at it, I can guess that
usandsyare supposed to beuserandsystemtime. And I guessidis supposed to beidle.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
1tand get effectively the same view as inhtop.I might learn
top’s filtering workflow, too. But so far, I always killed processes withps -ef | grep <process-name>and thenkill <pid>, which isn’t particularly more cumbersome, so will see…lol, same!
1tgets me 90% of the functionality I use inhtop.Wa is IO Wait. CPU time burned spent waiting for disk
Hi is hardware irq, similar concept but for hardware devices.
you could check
pgrep <process-name>tooThat is a good tip. Unfortunately, I am too
fishto understand it. 🙃I just type
psand in 9 out of 10 cases, my shell suggestsps -ef | grep <process-name>. So, it’s actually less for me to type than “pgrep”…Far from me to try to
basha suggestion’s on one’s head but^rpgor^r<process-name>(forreverse-i-search) is probably quite fast, obviously depends entirely on your typical usage. Hard to do less than 2 keystrokes I admit.Why not use pkill?
Ah, that was a brainfart. I do use
pkillprimarily. I just use the other command, when I’m not sure what the process is called…From top man-page global commands:
Also, pgrep and pkill may be handy.