Bug 438849

Summary: Show total number of processes in "Processes" view
Product: [Applications] plasma-systemmonitor Reporter: Mohammed Sameer <glifwentry>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: ahiemstra, aspotashev, kde, nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.22.1   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Ksysguard_Process_View

Description Mohammed Sameer 2021-06-18 09:12:18 UTC
Created attachment 139468 [details]
Ksysguard_Process_View

SUMMARY
Show total number of processes in "Processes" view of System Monitor. It would be very useful.

Also old ksysguard shows number of processes like "200 processes" in processes view, please see the attached screenshot.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-55-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2021-07-01 14:43:15 UTC
What would be a use case for this information?
Comment 2 Mohammed Sameer 2021-07-02 15:26:20 UTC
I don't know exactly, but I think it would be informative to know how many user processes are running, how many total processes are running, how many root processes are running in a system etc.
Comment 3 David Edmundson 2021-07-02 22:42:58 UTC
We've been putting some effort into trying to create a UX that doesn't show information for the sake of information, but only things that can actually influence actions.

We'll keep an eye on further feedback, but I will close for now.
Comment 4 Alexander Potashev 2025-05-29 22:41:36 UTC
> What would be a use case for this information?

Use cases of showing process count (after filter):
* Mention process count in bug reports where it may impact performance (e.g. https://bugs.kde.org/show_bug.cgi?id=504859)
* Estimate CPU/RAM footprint of an app. E.g. filter by "chrome" and see how many processes Chrome has which might be approximately the number of running (non-paused) browser tabs.
* Verify that filter change doesn't have effect. E.g. check that filter by "chrome" and filter by "crashpad" produce the same number of processes.