A parallel disk usage analyzer with interactive TUI for fast exploration and deletion of unwanted data.
dua (Disk Usage Analyzer) is a command-line tool for analyzing and managing disk space usage. It scans directories in parallel to provide fast insights into storage consumption and includes an interactive terminal interface for exploring files and deleting unwanted data. It solves the problem of slow disk analysis by maximizing hardware throughput and offering a safer alternative to bulk deletion commands.
System administrators, developers, and power users who need to quickly identify and free up disk space on their machines, especially those working with large directories or SSDs.
Developers choose dua for its parallel scanning speed, interactive TUI for safe exploration, and faster deletion compared to traditional tools like `rm`. Its Rust-based implementation ensures efficiency and cross-platform compatibility.
View disk space usage and delete unwanted data, fast.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses multiple threads to max out SSD throughput, providing faster analysis than traditional tools like `du`, as noted in the README for maximizing performance.
Features a multi-stage confirmation process in TUI mode to prevent accidental data loss, making deletions safer than using `rm` directly, emphasized in the README's safety focus.
Available on macOS, Linux, and Windows via various package managers like Homebrew, Scoop, and Cargo, ensuring easy installation across systems, as detailed in the installation section.
Supports TOML configuration files for customizing behavior, such as escape key navigation, allowing user flexibility, as shown in the configuration options.
Interactive mode only looks good in dark terminals and has issues with graphemes like Chinese characters, leading to incorrect column sizing and poor usability in diverse setups, per the README limitations.
Does not show symbolic links at all if no path is provided, and they are not followed, which can result in incomplete disk usage analysis, as admitted in the limitations section.
Requires about 60MB of memory per million entries in interactive mode and has a hard limit of ~4 billion files due to u32 indexing, posing issues for very large file systems, based on the README's noted limits.