81–84 of 84 posts
Earlier quoted context omitted.
You've also reminded me that while they do show up as CPU time, they wouldn't be 'user' time (for example in the output of the command 'time')
If it's user-mode loads and stores, which for applications is pretty common, it is user time. Easy to test.
that's a pretty awesome summary. to that i would add: * `iftop` that allows me to quickly check which network streams are hogging the machine (this is a little like sar -n DEV 1 but much more detailed!) * `tcpdump -c 100 -vv`- poor man's alternative to iftop or systat if they're not available locally * tail those logfiles, with systemd it's even easier with journald as all logfiles can be checked at once: `journalctl…
If you like iftop, iptraf is similar and goes deeper in the ability to dig into TCP details or confuse yourself with scads of BPF rules.
that's a pretty awesome summary. to that i would add: * `iftop` that allows me to quickly check which network streams are hogging the machine (this is a little like sar -n DEV 1 but much more detailed!) * `tcpdump -c 100 -vv`- poor man's alternative to iftop or systat if they're not available locally * tail those logfiles, with systemd it's even easier with journald as all logfiles can be checked at once: `journalctl…
I'll add to your list with htop. Its a little nicer than plain ole top.
Earlier quoted context omitted.
And `glances` is pretty great for big-picture stuff, all-in-one. It's not as precise on CPU/memory as htop, but you get network bandwidth, disk I/O, disk usage and more.
No love for dstat? Glances looks cool though, thanks for that one.
dstat i already knew about, somehow forgot it in the listing, definitely a must as well.