Numbers, with their terms attached
Performance claims are easy to write; the hard part is saying where they came from. Every figure below carries its measurement conditions — including what we never measured.
The environment first:everything below comes from internal benchmarking on the development machine — a MacBook Pro 15″ 2018 (Intel i9-8950HK, 12 logical cores, 32 GiB, macOS 15.7.9), Release build, machine idle, query cases warmed up 5 times and then measured 30+ times. This is an Intel machine, and the figures do not represent Apple Silicon performance; we have not re-run them on Apple Silicon. What you experience depends on your hardware, your drive and your file count.
Keystroke to results
| Item | Value | Terms |
|---|---|---|
| Internal query-latency threshold | 1M entries p95 ≤ 5 ms 5M entries p95 ≤ 20 ms | A line the product holds itself to — not a single best run |
| Path-scoped queries | 1M entries p95 13.5–13.9 ms 5M entries p95 64.6–66.8 ms | in:4095, three repeat rounds, identical result fingerprints each round |
| Repeatedly narrowing the same scope | p95 330 ms → 81 msSame machine and data, −75.4% | 5M fixed dataset, in:4095 report, reusing an already-verified base bitmap |
| Recompute after changing a display filter | 12.9 s → 0.6 s | Toggling switches such as "include/exclude cloud file names" on a settled index; results bit-identical to per-record evaluation |
From a file changing to being searchable
Indexing, memory and index size
| Item | Value | Terms |
|---|---|---|
| Index write | 5M entries in 3.5 sHistorically 39.5 s | This is write time, not first-scan time — measured on a fixed synthetic dataset |
| First full scan of a real disk | Depends on drive and file countA whole disk can reach the tens-of-minutes range | We do not publish a fixed cross-machine number, because that would be invented. Everyday folders are searchable while it runs |
| Idle CPU | 0.08% – 0.54% single-core equivalent | Free-tier scope (133k entries) measured ≈0.077% over a 91-second window; ≈0.42% in a 60-second window after a full-disk build |
| Memory just after launch | ≈23.7 MB physicalPeak 24.0 MB | Sampled with vmmap -summary, before any index was built; wider index scope costs more |
| Steady-state memory threshold | ≤ 200 MB at 1M entries | A line the product holds itself to; transient build peaks adapt to available system memory and are released immediately |
| Index size | ≤ 150 MB at 1M entries≈23 MB for the free tier's 133k entries | The index holds only names, paths, sizes and timestamps — no file contents |
Stating the gaps too
- Nothing here has been re-run on Apple Silicon. Every figure above comes from the same Intel machine.
- There is no cross-machine "your first full scan will take N minutes" number — it depends on your drive type, file count and system state.
- "5 million" describes an index scale exercised repeatedly in development benchmarking. It is not a prediction about your disk.
- We avoid absolute claims like "the fastest": we publish only what we measured ourselves, and make no comparative speed claims against other tools.
The fastest way to verify is to install it
The free tier is free forever. The status bar shows the live result count and how long the query took — the number on your own Mac is more convincing than ours.