THE NUMBERS

How fast is Findra?

Everything below came out of findra --searchbench and was pasted without editing. No number appears on this page that you cannot reproduce on your own computer with that one command.

Type part of a filename. The matches are back.

Median round trip for every query measured, across 1,339,635 names, from the moment the query leaves the window to the moment the results arrive.

invoice2.13 ms

sunset2.77 ms

report3.36 ms

config3.73 ms

readme3.77 ms

2.4 s From cold to ready 1,339,635 names read off the disk when the helper starts. Longer right after a restart, when nothing is cached.

172.0 MB What it costs to hold The name index for 1,339,635 names, measured by the helper that holds it.

0 Bytes about your files No account, no cloud, no analytics, no crash reporting, no telemetry.

FILENAMES

Name search, query by query

The round trip is the whole journey: from the window, through the pipe to the helper that holds the names, and back. The index scan is the helper's own share of it.

Name query	Round trip p50	Round trip p95	Index scan p50	Worst	Hits
invoice	2.13 ms	2.45 ms	1.77 ms	2.77 ms	50
sunset	2.77 ms	3.00 ms	2.41 ms	3.99 ms	23
report	3.36 ms	3.74 ms	2.98 ms	4.18 ms	50
config	3.73 ms	4.61 ms	3.26 ms	4.76 ms	50
readme	3.77 ms	4.20 ms	3.26 ms	4.75 ms	50

INSIDE FILES

Full-text search

Against this machine's own content index, read from a real disk, so the slowest word is in there beside the fastest.

Word	p50	p95	Worst	Hits
lease	1.12 ms	1.31 ms	2.67 ms	50
agreement	4.18 ms	4.66 ms	5.23 ms	50
invoice	0.82 ms	0.91 ms	1.77 ms	50
total	8.89 ms	11.80 ms	12.75 ms	50
report	14.95 ms	15.94 ms	16.98 ms	50

Machine AMD Ryzen 9 9900X3D RAM 47.1 GB Disk NVMe SSD OS Windows 11 Pro 10.0.26200.9445 Accelerator none loaded Build Findra 0.5.1 Samples n=50 per query

A number without its machine is marketing rather than measurement, so the machine is named. Yours will differ. The whole run, every table and the stores it measured, is in the README, pasted as the command printed it.

Findra tries DirectML for the vision and meaning models and Vulkan for speech, and falls back to the processor when neither answers, which is a supported configuration rather than a failure: only the first pass through your files is slower, and findra --searchmodels prints which provider it chose and every one it turned down, with reasons.

These numbers are from one machine, and it has an NVIDIA card. Findra is built for AMD and Intel processors, for AMD, Intel and NVIDIA graphics, for integrated graphics, and for machines with no usable accelerator at all - but only this configuration and the processor-only path have been measured. AMD and Intel graphics have not been tested on real hardware. On arm64, only the test suite and the headless diagnostics have run, on every push, on a GitHub runner with no graphics card; nothing here was measured there. The paths Findra uses are vendor-neutral by design so that they should work there; that is a decision rather than a measurement, and it is said here as one.