-
-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow summing-collapse of a process/thread tree #920
Comments
You can collapse a tree branch with |
@fasterit : Rephrasing to emphasize the main request. |
@fasterit : #303 is about global merging, with no option of expansion. #301 is also global, and would not be affected by collapsing; also, it involves merging more than is currently being merged, while my proposal is orthogonal of that. That being said - if #301 were implemented I would not bother to file this issue. |
@fasterit This feature request is different from #301. This is more about usability improvement for tree view when a process/thread "subtree" is collapsed.
|
i want this feature so much i could create PR |
I would also love it if the default behavior was changed so that the percentages were cumulative! 🙏🏻 |
I want this too. |
That depends on how many pull-requests we get for this feature. |
I often want to see the total memory and CPU usage for some process and its subprocess (e.g. Firefox, Chromium). I can htop to consider all threads of a process together (although even that is a global setting) - but I can't do that for processes. I wish that, in tree view, when I collapse a node (with the
-
key) - I will see the sum of the memory usage percentage, CPU usage percentage etc of its entire subtree.Now, I realize that for some columns, summation may not be obvious (e.g. if a process started T seconds ago and runs N subprocesses after T/2 seconds, it's not clear whether the time is (N+1)*T/2 or T), or not relevant, but any reasonable default will do AFAIAC. Plus people can always file other bugs about that later on...
The text was updated successfully, but these errors were encountered: