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
In #8114 it was stated that "Personally, I think cgroup view is much more informative. Process names are often named really strangely and is not very informative.". This can be true, but not in every case.
Consider for example this cgroup view that below presents:
Here, the terminal kitty does the right thing™ and creates a scope for every terminal window. However, just looking at the cgroup view, does not tell me what exactly it is that kitty-106668-0.scope is performing creating some CPU load.
If the processes with their arguments where listed as descendants of kitty-106668-0.scope, I would in many cases immediately get an idea what is running there and what it is doing. Right now, I have to zoom (via z) into the cgroup to see its processes.
BTW, thanks for below, it is IMHO currently the best tool for cgroup-based performance-metric analysis.
The text was updated successfully, but these errors were encountered:
In #8114 it was stated that "Personally, I think cgroup view is much more informative. Process names are often named really strangely and is not very informative.". This can be true, but not in every case.
Consider for example this cgroup view that below presents:
Here, the terminal
kitty
does the right thing™ and creates a scope for every terminal window. However, just looking at the cgroup view, does not tell me what exactly it is thatkitty-106668-0.scope
is performing creating some CPU load.If the processes with their arguments where listed as descendants of
kitty-106668-0.scope
, I would in many cases immediately get an idea what is running there and what it is doing. Right now, I have to zoom (viaz
) into the cgroup to see its processes.BTW, thanks for below, it is IMHO currently the best tool for cgroup-based performance-metric analysis.
The text was updated successfully, but these errors were encountered: