USearch
Fast Open-Source Search & Clustering engine × for Vectors & Arbitrary Objects × in C++, C, Python, JavaScript, Rust, Java, Objective-C, Swift, C#, GoLang, and Wolfram 🔍
Runssource: GitHubhomepageC++Apache-2.0commit f91fe5bc0002
C++, Apache-2.0 licensed. The project labels itself: approximate nearest neighbor search, clustering, database, faiss, full text search, fuzzy search, image search and kann.
USearch runs. An Argusic agent installed it in 18 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
USearch v2.26.2 Python package installed from prebuilt wheel, 772/772 pytest tests pass, 15/15 SQLite extension tests pass after building libusearch_sqlite.so locally, and the C++ native test suite passes with exit code 0. JavaScript native addon build timed out (missing numkong submodule compile).
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Python.h not found (python3-dev not installed) preventing C++ extension build from source5 minutes
- usearch.sqlite_path() referenced non-existent binary for SQLite extension4 minutes
- Install time
- 18 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pytest python/scripts/ -v --tb=line: 772 passed, 31 skipped in 49.79s; /tmp/build_cpp/test_cpp: exit code 0 after running all test suites including binary vectors, sparse vectors, key lookups, load/view, truncated index
- Model tokens used
- 109,631
- Exact commit tested
- f91fe5bc0002
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Testing view of a truncated index file
C++ tests pass with exit code 0. Let me calculate my timestamps and build the final report.
exec
/bin/sh -lc 'date +%s' in /work/repo
succeeded in 0ms:
1790764443
exec
/bin/sh -lc "printf '%s' '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minut…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 18, "errors": [{"msg": "Py…
tokens used
109,631Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 18 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
approximate-nearest-neighbor-searchclusteringdatabasefaissfull-text-searchfuzzy-searchimage-searchkannnearest-neighbor-searchrecommender-systemsearchsearch-enginesemantic-searchsimdsimilarity-searchtext-searchvector-searchwebassembly
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/usearch)Questions
- Does USearch run?
- Yes. USearch runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test USearch?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f91fe5bc0002. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test USearch?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does USearch take to install?
- 18 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does USearch need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing USearch?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for USearch?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.