parallel-disk-usage
walkdir
Our great sponsors
| parallel-disk-usage | walkdir | |
|---|---|---|
| 7 | 5 | |
| 343 | 1,171 | |
| - | - | |
| 7.4 | 4.7 | |
| 14 days ago | 6 days ago | |
| Rust | Rust | |
| Apache License 2.0 | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
parallel-disk-usage
-
Ask HN: What Underrated Open Source Project Deserves More Recognition?
pdu: https://github.com/KSXGitHub/parallel-disk-usage
Great compliment to ncdu for a single-view disk report and blazing fast.
-
Ncdu – NCurses Disk Usage
ncdu is one of the most useful CLI tool out there! Been using it for many years as well.
Another disk scanner worth plugging that I came across for some use cases where I needed to generate single-view reports is pdu - it has the same concurrency implementation that other ncdu alternatives use so the performance is much better too.
https://github.com/KSXGitHub/parallel-disk-usage
-
Your favorite Rust CLI utility? I have my top 10 below.
pdu is dust but much faster
- Parallel Disk Usage (pdu) is a highly parallelized, blazing fast directory tree analyzer written in Rust
- Parallel Disk Usage (pdu) — A highly parallelized, blazing fast disk usage visualizer written in Rust
-
Parallel Disk Usage (pdu) — A highly parallelized, blazing fast disk usage visualizer
Thanks for telling me this. I create a new benchmark.
walkdir
-
Project idea: port markdownlint to Rust
https://github.com/BurntSushi/walkdir for discovering markdown files
-
Blazingly fast file search library built in Rust 🔥
The API looks really nice! What is your vision for the project? How is it going to compare to (walkdir)[https://github.com/BurntSushi/walkdir] performance and feature-wise?
-
Git ls-files is Faster Than Fd and Find
> I believe that GNU find is slow because it is specifically written to allow arbitrary filesystem depth as opposed to "open file descriptor limit-limited depth".
I haven't benchmarked find specifically, but I believe the most common Rust library for the purpose, walkdir[1], also allows arbitrary file system recursion depth, and is extremely fast. It was fairly close to some "naive" limited depth code I wrote in C for the same purpose.
I'd be curious to see benchmarks of whether this actually makes a difference.
[1] https://github.com/BurntSushi/walkdir
-
Your favorite Rust CLI utility? I have my top 10 below.
It relies pretty heavily on the walkdir library from burntsushi so kudos to them!
-
Rust, musl and glibc in 2021
Although, I don't think FileType is the only problem. There's also Metadata, which I also had to re-roll: https://github.com/BurntSushi/walkdir/blob/1d7293a5a1ef548ce587a0b08abce5f21571a100/src/os/unix/stat.rs
What are some alternatives?
kondo - Cleans dependencies and build artifacts from your projects.
cligen - Nim library to infer/generate command-line-interfaces / option / argument parsing; Docs at
grex - A command-line tool and Rust library with Python bindings for generating regular expressions from user-provided test cases
zenith - Zenith - sort of like top or htop but with zoom-able charts, CPU, GPU, network, and disk usage
GraphScope - 🔨 🍇 💻 🚀 GraphScope: A One-Stop Large-Scale Graph Computing System from Alibaba | 一站式图计算系统
loggedfs - LoggedFS - Filesystem monitoring with Fuse
tools
exa - A modern replacement for ‘ls’.
hexyl - A command-line hex viewer
sauce - A tool to help manage context/project specific shell-things like environment variables.
walk - Plan 9 style utilities to replace find(1)