2 ms·
I'm not sure how it works beyond that it reads /proc, but whatever it does it uses a whole lot more compute than nethogs does (which also displays per process a
by freedomben 3y ago
I'm not sure how it works beyond that it reads /proc, but whatever it does it uses a whole lot more compute than nethogs does (which also displays per process and also uses /proc as the information source). This is fine for most of my machines, but for lower-specced machines I'll probably have to stick with nethogs[1]
[1]: https://github.com/raboof/nethogs https://github.com/raboof/nethogs
- mr337 3y agoIf it the popey from podcasts he used to work at Canonical. Actually looking at this confused, popey also came up with the snap removal tool that is handy https://github.com/popey/unsnap https://github.com/popey/unsnap Maybe he has a love hate relationship with snaps lol Edit: added gh info
- freedomben 3y agoYeah I would strongly bet it is the same Popey from the JB podcasts. Last I heard him he was pretty pro-Snap and was Snapping different projects for people, so this is completely in-line with my expectations. Seems pretty unlikely to be a coincidence :-)