You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The above, with tree sorted by memory usage in human readable form, stat legend or omitted, colors, vsz+rss merged (or replaced with mem+swap), tty removed (no idea how it is useful, but -v, --verbosity flag may turn it back).
The goal is to give a clear understanding which tree is using the most memory. Much like neofetch gives understanding which OS and hardware is used. For that it probably makes sense to sort tree such that last screen contains the branch and processes with most memory usage. It would also help to see the graph of most memory usage over time, with spikes or OOM events, maybe in interactive interface like visidata.
The text was updated successfully, but these errors were encountered:
Problems with
ps
.➜ ~ ps PID TTY TIME CMD 487827 pts/4 00:00:00 zsh 495775 pts/4 00:00:00 ps
ps faux
, but I can't explain what it does without https://explainshell.com/explain?cmd=ps+faux (and even with it)Draft of the ideal solution.
The above, with tree sorted by memory usage in human readable form, stat legend or omitted, colors, vsz+rss merged (or replaced with mem+swap), tty removed (no idea how it is useful, but -v, --verbosity flag may turn it back).
The goal is to give a clear understanding which tree is using the most memory. Much like
neofetch
gives understanding which OS and hardware is used. For that it probably makes sense to sort tree such that last screen contains the branch and processes with most memory usage. It would also help to see the graph of most memory usage over time, with spikes or OOM events, maybe in interactive interface likevisidata
.The text was updated successfully, but these errors were encountered: