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
My two cents:
Something that is currently missing from all GUI system monitors in Linux (but exists at a limited level in Win10) - a real, working and useful network usage breakdown:
Per process (matching the current process list)
Per process group (e.g., container)
Per connection target (e.g., "facebook.com")
Also, a display of all registered sockets/handles (lsof style) in their current state, broken down to process or target, would be very useful.
The text was updated successfully, but these errors were encountered:
There will be definitely a redesign of the process tab! This tab could be so much more useful than it is right now and I think your ideas would be a great addition.
My two cents:
Something that is currently missing from all GUI system monitors in Linux (but exists at a limited level in Win10) - a real, working and useful network usage breakdown:
1. Per process (matching the current process list)
2. Per process group (e.g., container)
3. Per connection target (e.g., "facebook.com")
Also, a display of all registered sockets/handles (lsof style) in their current state, broken down to process or target, would be very useful.
These ideas are great and useful, but the Linux kernel doesn't store the process-wise network information.
To show the process-wise network activity nethogs can be used which basically monitors every process and check how much data is the process receiving and sending. This indeed works good but is a heavy workload on CPU.
This project https://github.com/rejuce/LikeTaskManager does use nethogs.
So it for low end machine this approach is not suitable.
Looks like a great start!
My two cents:
Something that is currently missing from all GUI system monitors in Linux (but exists at a limited level in Win10) - a real, working and useful network usage breakdown:
Also, a display of all registered sockets/handles (lsof style) in their current state, broken down to process or target, would be very useful.
The text was updated successfully, but these errors were encountered: