[HN Gopher] Btop++: Resource monitor for processor, memory, disk...
___________________________________________________________________
Btop++: Resource monitor for processor, memory, disks, network and
processes
Author : ingve
Score : 85 points
Date : 2023-06-25 11:50 UTC (11 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| parentheses wrote:
| I recall looking at this before support for macos and was
| slightly disappointed. Now that they have it, I'm going to
| install it immediatement!
| gavinhoward wrote:
| I use this. It's _much_ lighter than its predecessor, bpytop.
|
| You can track this by running both and htop with the total CPU
| time tracker on htop. btop uses less CPU than htop. bpytop uses
| much more.
|
| This becomes a bigger deal the longer a machine is running. I
| specifically use btop for this when fuzzing because any CPU it
| doesn't use goes to the fuzzer. And I still want to track the
| state of the machine while fuzzing, _especially_ while fuzzing
| since it 's under extreme load.
| pbbakkum wrote:
| If you're looking for a lighter weight TUI for Top information
| check out a recent project of mine here:
| https://github.com/bakks/poptop
| tambourine_man wrote:
| Looks awesome, thanks for sharing.
| mike_hock wrote:
| > Set suid bit to make btop always run as root
|
| > No need for sudo to enable signal sending to any process
|
| How to not security
| worldsavior wrote:
| Why couldn't he just say to use sudo?
| lostdog wrote:
| Very cool, but it does flicker for me, and setting
| background_update to false didn't help.
|
| (Every 2 seconds, it flicker 1-3 times)
| JNRowe wrote:
| If you're installing a distro package or one of the builds
| mentioned in the link, I encourage you to try building it
| yourself. The build system is really well thought through, and
| unusually for a fancy art-ified Makefile it correctly handles the
| things you'd want as a distro packager too.
| sshine wrote:
| btop++ is great.
|
| For measuring parallel CPU utilisation, I still prefer htop
| because it dedicates more screen space to "here and now" CPU
| usage for each core.
___________________________________________________________________
(page generated 2023-06-25 23:01 UTC)