fast

Measure the current download speed

$ fast

$ fast [[-u|--upload]]

$ fast --single-line

fast pattern

pattern
    The search string. This can be a simple filename, a part of a directory name, or a more complex pattern using wildcards.
For example, 'fast *.txt' will find all files ending in '.txt'.

The `fast` command is a significantly faster alternative to `find` for locating files and directories within a file system. It achieves this speed by using a pre-built index of the filesystem, typically updated regularly (e.g., daily). This index is usually created and maintained by the `updatedb` command (or a similar utility). Because it relies on this index, `fast` might not reflect the absolute latest changes to the filesystem, but it offers a dramatic speed advantage for most search tasks. `fast` is generally used when you need to find a file quickly but don't necessarily need the absolutely most up-to-date results. Think of it like searching a well-organized library catalog versus painstakingly looking through every book on the shelf. The output displays the full path of the matching files and directories.

The results are only as current as the index used. Run `updatedb` periodically to update the index.
The exact behavior and available options might vary slightly depending on the specific implementation of `fast` (e.g., `mlocate` or `plocate`).

It is important to regularly update the database used by `fast` (usually through `updatedb`). This ensures that the search results are relatively current.
The `updatedb` command is typically run automatically as a scheduled task (e.g., via cron or systemd timers).

The default case sensitivity of `fast` depends on the implementation and system configuration. Some implementations are case-insensitive by default, while others are case-sensitive.
Consult the manual page for the specific `fast` variant you are using to determine its behavior and how to change it.

The `fast` command is often a symlink or alias to a faster implementation of `locate`, such as `mlocate` or `plocate`. These implementations were developed to address the performance limitations of the traditional `locate` command, which could be slow on large filesystems. The key improvement is the use of a pre-built database, allowing for rapid searches. `mlocate` and `plocate` prioritize security by only indexing files that the user has permission to read, making them suitable for multi-user environments.

locate(1), find(1), updatedb(1)