[imrehg]

I've relatively recently migrated over to using btop[0], and it's the kind of modern interface, useful and informative, that I needed.

As others mention it - it seems to shows the Watts used as well :) (and network, and GPU, and disks,....)

[0]: https://github.com/aristocratos/btop

[bilegeek]

I like btop, but there are downsides:

1.) No zram/zswap statistics. (Though htop only supports zram also.)

2.) No ZFS statistics breakdown.

3.) Doesn't support Arc GPU yet.

4.) I can't disable the disk fill bars, which makes the I/O rate graphs extremely squished unless the console window is very large.

[reaperducer]

5.) Requires an 80x24 window. Not ideal for monitoring several machines at once.

htop scales all the way down to 40x8 on my TRS-80.

[JdeBP]

It's bad the other way, too. btop on a 50×232 terminal over an actual 57600 BPS serial line is unusable, even in 16-colour mode. It does not have even the most basic of full-screen TUI redraw optimizations, and outputs the entire screen again and again.

[internet101010]

Long time user of btop. Only thing it is missing is a ports column next to the others. Also I think the cpu/gpu graph graph is way oversized and would like more space occupied by the open file table in general.

[hinkley]

I still occasionally use alpine as a base image for containers and it looks like both doesn’t do musl so that’s out.

[MomsAVoxell]

Yup, btop zealot here, it even replaced iStatMenu on my brand new MacBook ..

[NetOpWibby]

Oh wow, now I gotta check it out.

[zackify]

Same. Btop is the best

[JdeBP]

Well, unless one is using FreeBSD or OpenBSD, where the btop code is still using 32-bit integers to calculate 64-bit sizes, and falling prey to unsigned integer wraparound. htop's code calculates using size_t, which ends up as a 64-bit integer on 64-bit architectures.

* https://news.ycombinator.com/item?id=48778757 (https://crocidb.com/post/freebsd-ate-my-ram/)

* https://github.com/aristocratos/btop/pull/1728