Repository navigation
fdu 0.2.1
fdu 0.2.1 is a patch release focused on Linux. The default fdu PATH and --view summary are about three times faster on source trees with many .gitignore files, the default summary no longer builds a full index to report its ignored share, and building the full index is faster on trees of many small directories. A .gitignore spelled in another case now applies where git applies it, and an answer served from the cache with --stale-ok always says it is stale. There are no incompatible changes to the command line, the report schemas, or the Rust and Python APIs.
Performance
Three engine changes were each measured on their own, on a quiet 4-vCPU virtualized ext4 host with warm caches:
- Ignore rules without allocation, resolved once per directory. On the Linux v6.12 source tree (92,474 entries, 358
.gitignorefiles) the default tree fell from 590 to 211 ms and the default summary from 505 to 167 ms, with identical answers (exp-173, exp-174). - A summary that reads ignore rules without an index. On a million-entry tree with no
.gitignorethe default summary took 19% less time and its peak memory fell from 314 to 8.6 MiB; on the source tree, 7% less time and 23% less memory (exp-187). On macOS its peak memory fell 58–69%. - Directory listings freed where they were allocated. The default indexed tree took 8.6% less time on a
node_modulestree of small directories, and a screen on the generated million-entry tree measured 10.6% less; building the index alone took about 7% less on both. Trees with few, larger directories are unchanged (exp-190).
Against its peers on the generated million-entry Linux tree, 0.2.0’s summary (--no-gitignore --view summary) was already the fastest tool measured, 8% ahead of pdu and 12% ahead of diskus, while its indexed tree took 23% longer than pdu. The listing change above cuts that job by about a tenth; the peer comparison has not been re-run on 0.2.1. The pdu brief explains where the remaining Linux gaps come from and what comes next. On macOS, where fdu was already the fastest tool measured, these changes were not re-measured for this release.
Highlights
- Case-variant
.gitignore. On a case-insensitive volume (APFS and NTFS by default, an ext4 casefold directory), a.gitignorespelled.GITIGNOREor in any other case now governs, as it does for git; on a case-sensitive volume it stays an ordinary file. Every route agrees, and the rules are reported under.gitignore. - Stale answers say so. A
--stale-okanswer printswarn: stale answer: served from the snapshot without filesystem verificationon stderr on every format, and--quietkeeps it. Python reports carry it in the newReport.warnings.
Install
uvx --no-build fdu@latest --help # run the latest release without installing it
uv tool install --no-build fdu # the command line from a prebuilt wheel
cargo install --locked fdu # the command line, built with Rust 1.85 or newer
pip install fdu # the Python package: import fduRe-run uvx --no-build fdu@latest --install-skill after upgrading so the agent skill describes this release.
Compatibility
This is a patch release: no command-line option, report or cache schema, or Rust or Python API changed incompatibly, and cargo-semver-checks finds no breaking change in fdu-core or fdu against 0.2.0. Two additions: Python Report.warnings and Rust report_format::report_warnings.
Upgrading from 0.2.0
- First run scans cold. As with every release, the engine fingerprint changes, so 0.2.1 reuses no snapshot or content sidecar written by 0.2.0: each cached tree’s first run walks it, and its first analyzed run reads every file again.
- Stderr. A script that expects empty stderr from a
--stale-okrun now sees onewarn:line; paths and long output no longer printnote: cache-only result.
Known Limitations
- Linux. On source trees with many
.gitignorefiles the default command still takes about three times pdu’s time, because classification runs on one thread. Building the full index on the generated tree took 23% longer than pdu in 0.2.0; by the listing change’s measured saving that gap is about 10%, not yet re-measured against peers. - Memory on Linux source trees. The ignore-aware summary holds about 20 MiB more than a walk without
.gitignoreon the Linux v6.12 tree, which is not yet explained. - The 0.2.0 limitations on links, cache retention, watch backends, opened roots, and JSON integers still apply.
Security
Publishing now refuses a release tag that is lightweight, off main, or signed with a signature GitHub cannot verify, checks the Rust API with cargo-semver-checks before uploading, and publishes to crates.io only through trusted publishing. Report vulnerabilities through GitHub’s private vulnerability reporting, as SECURITY.md describes.
Full changelog: CHANGELOG.md
Full commit history: changes from v0.2.0 to v0.2.1