dust VS procs

Try using dust https://github.com/bootandy/dust

Folks open to using gdu might like to try dust (6k stars), or even erdtree (1.4k stars) which is too recent to show up on lists like this and still a bit behind on stars. A lot of people seem to use starship (33k stars) though I'm personally oldschool on prompts. There are many other items on that list I'm not motivated to check.

The first thought I had was to use rayon for this. And looking at some prior art that does pretty much the exact same thing, it does indeed use rayon.

The dust CLI command (made with Rust) can do this too.

How does this compare to dust?

Happened to me this morning, something filled up my drive in minutes. I used dust[1] to look for large files while it was happening but knowing what was doing it would've been a big help.

[1] https://github.com/bootandy/dust

dust is also really nice.

You can have a look at this repo for some inspiration, since it's mostly cross platform. It uses the winapi crate for Windows and the procfs for Unix.

procs is a ps replacement. It provides colorized human-readable output, multi-column search, more information than ps, docker support, paging, watch mode, and tree view. It is a much more user-friendly and modern alternative to ps. You can filter by name and PID and use logical and/or operators to combine multiple filters. It also has a tree view which is very useful for seeing the process hierarchy. It can also show docker container names for the process running docker containers.

ps replacement - Procs

prox: A modern replacement for ps written in Rust.

For example, add the below entry to the TOML config file if you want to download the procs tool as well.

Preview process trees (using procs)