htop because it's much more user-friendly than top, has the feature of sending all kinds of signals to processes, has mouse support and it generally looks good. Not a fan of btop at all. Idk how to use it and I don't like the UI. I personally love the idea of no bloat. It's just such a nice little philosophy. Sometimes I even want to use a CLI only computer tbh. Though htop weights only a few kilobytes and it has features top doesn't have so I don't consider it bloat. I had it on my server as well

https://github.com/ClementTsang/bottom

bottom

Btop

It's no burden. Don't overthink it. Use whatever you like.

htop is my go-to these days. It tells me what I need to know, and it's just nice to look at.

btop for bling

htop for practical utility

top for minimalism, availability, reliability

htop on our vms and clusters, because it's in all the repos, it's fast, it's configurable by a deployable config file, it's very clearly laid out and it does everything I need. I definitely would not call it bloated in any way.

My config includes network and i/o traffic stats, and details cpu load type - this in particular makes iowait very easy to spot when finding out why something's racking up big sysloads. Plus, it looks very impressive on a machine with 80 cores...

My brain can't parse top's output very well for anything other than looking for the highest cpu process.

But - ymmv. Everyone has a preference and we have lots of choice, it doesn't make one thing better or worse than another.

I like htop because it has nice CPU graphs and a good tui for navigating. Top is a bit too obtuse for a new user, especially since CPU time is measured per core and not per the entire CPU. Plus I never figured out how turbo boost plays a roll in those percents.

I haven’t gotten around to messing with btop, but it seems like more of what I like.

Also fuck the “muh bloat” people. I have an i9 and 32 gigs of ram. I don’t care that a monitor util takes 1/10th of a second longer to launch and uses 1MB more of ram.

htop gives me enough info without being too busy or slow, it's also in basically every OS repo by default so no complicated install.

The other ones can look awesome, but they're often harder to get info from quickly due to being too cluttered.

btop because pretty colors :3

i still need to learn how to use top well though, just in case that's the only option some day. if all else fails i just resort back to ps and (p)kill.

htop because pretty colors and graphs.

Or top because it's like muscle memory now.

I tend to go with htop purely out of habit. btop is better but I simply don't think to use it.

I'm more of a bottom, if you know what I mean.

I'm more of a bottom guy myself

Htop, but only because its what I've always used and have no need to change at the moment.

glances

Htop is completly customizable for how the sections of data are displayed. it is a bit convoluted the first time you start, but then it makes

btop for system resource monitoring, htop for actually finding and killing processes

I love btop because of how fancy the graphs look and it also shows disk utilisation. I use it pretty much wherever I can. When I want something more simple I use bottom btm --basic and alias it to top

I like btop because of its ease of use and modern gui. When I open top or even htop it feels like I'm using something designed for a dumb terminal from the 70s. When opening btop it feels like something designed for how computers are used now and not 50 years ago.

Also to my knowledge It's the only full system monitor to include GPU monitoring (while other GPU monitors exist they usually only monitor the GPU and not the whole system)

Much better to quickly determine CPU and memory load.

atop, especially because you can take snapshots over time of what the system was doing and use it to backtrack when bad things happen.

top

Because it exists in nearly every environment I might need to check usage. From my desktop, through laptops, lab machines, routers, embedded systems, IoT to cloud, I don't have to keep the muscle memory of more than one app.

bpytop, it's just too pretty to pass up.

Btop, it's pretty. Htop when I'm lazy or working on a system that's bare bones.

I use btop all the time, used htop before I knew about btop, almost never use top.

They’re different tools with different purposes. What you’re asking is like “which do you prefer, hand driver, box/open end wrench, socket wrench or impact driver?”

Ps and top can be used to very easily figure out and address when processes are screwing up. Atop, htop and btop can be used to directly view stuff hardware reports in real-ish time so you can figure out if a process has stopped being “stepped” across cores, a disk has stopped responding in time or when there’s a lot of network traffic.

As utilities they operate within fundamentally different scopes, to the point with btop of being extremely zoomed out macro pictures that are helpful when taking in abstract information about a system.