asitop VS bottom

There’s also asitop https://github.com/tlkh/asitop

Don't do this on my behalf but if you're ever curious yourself, on some other date, you can use iStat Menu among other utilities or readers to check GPU utilization, thats a lot easier to read than Activity Monitor. If using iStat, go to iStat Menus, click on the CPU/GPU dropdown, then the GPU in the active items bar, and select processor. You'll see a graph and you can just let that sit for a few minutes and average it by eye. I'm on a 4K display and it seems to be averaging about 10% GPU utilization.

Generally, chips start to throttle around 90 degrees. If you want to know exactly temp, use asitop.

oh dear, my bad, look into ASITOP , i am apparently very confused today for some reason, as i tried to install that apple-silicon-only tool on an intel imac this morning before being basically called an idiot by said terminal 😂

I don't have RE:village installed, but if you have game installed you can check it using ASITOP

I'll take a deeper look once https://github.com/tlkh/asitop/pull/44 has been merged.

I used ASITOP to measure power consumption. but it only supports Apple silicon Mac.

Asitop.

bottom

I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom

It works on Windows also.

If anyone is looking for a "top" like, written in Rust, might have a look at https://github.com/ClementTsang/bottom

Looks like bottom with another theme

bottom - A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.