A tiny, efficient fuzzy search that doesn't suck. This is my fuzzy 🐈. There are many like it, but this one is mine.
uFuzzy is a fuzzy search library designed to match a relatively short search phrase (needle) against a large list of short-to-medium phrases (haystack). It might be best described as a more forgiving String.indexOf(). Common use cases are list filtering, auto-complete/suggest, and title/name/description/filename/function searches.
In its default configuration, each uFuzzy match must contain all alpha-numeric characters from the needle in the same sequence, so is likely a poor fit for applications like spellcheck or fulltext/document search. However, its speed leaves ample headroom to match out-of-order terms by combining results from all permutations of the needle. When held just right, it can efficiently match against multiple object properties, too.
- Junk-free, high quality results that are dataset-independent. No need to fine-tune indexing options or boosting params to attain some arbitrary quality score cut-off.
- Straightforward fuzziness control without surprises.
- Sorting you can reason about and customize using a simple
Array.sort()which gets access to each match's stats/counters. There's no composite, black box "score" to understand. - Concise set of options that don't interact in mysterious ways to drastically alter combined behavior.
- Fast with low resource usage - there's no index to build, so startup is below 1ms with near-zero memory overhead. Searching a three-term phrase in a 162,000 phrase dataset takes 12ms with in-order terms or 50ms with out-of-order terms.
- Micro, with zero dependencies - currently ~4KB min
NOTE: The testdata.json file is a diverse 162,000 string/phrase dataset 4MB in size, so first load may be slow due to network transfer. Try refreshing once it's been cached by your browser.
First, uFuzzy in isolation to demonstrate its performance.
https://leeoniya.github.io/uFuzzy/demos/compare.html?libs=uFuzzy&search=super%20ma
Now the same comparison page, booted with fuzzysort, QuickScore, and Fuse.js:
Here is the full library list but with a reduced dataset (just hearthstone_750, urls_and_titles_600) to avoid crashing your browser:
npm i @leeoniya/ufuzzy
const uFuzzy = require('@leeoniya/ufuzzy');<script src="./dist/uFuzzy.iife.min.js"></script>let haystack = [
'puzzle',
'Super Awesome Thing (now with stuff!)',
'FileName.js',
'/feeding/the/catPic.jpg',
];
let needle = 'feed cat';
let opts = {};
let uf = new uFuzzy(opts);
// pre-filter
let idxs = uf.filter(haystack, needle);
// sort/rank only when <= 1,000 items
if (idxs.length <= 1e3) {
let info = uf.info(idxs, haystack, needle);
// order is a double-indirection array (a re-order of the passed-in idxs)
// this allows corresponding info to be grabbed directly by idx, if needed
let order = uf.sort(info, haystack, needle);
// render post-filtered & ordered matches
for (let i = 0; i < order.length; i++) {
// using info.idx here instead of idxs because uf.info() may have
// further reduced the initial idxs based on prefix/suffix rules
console.log(haystack[info.idx[order[i]]]);
}
}
else {
// render pre-filtered but unordered matches
for (let i = 0; i < idxs.length; i++) {
console.log(haystack[i]);
}
}uFuzzy has two operational modes which differ in matching strategy:
- intraMode: 0 (default) requires all alpha-numeric characters in each search term to exist in the same sequence in all matches. For example, when searching for "cat", this mode is capable of matching the strings below. What is actually matched will depend on additonal fuzziness settings.
- cat
- coat
- scratch
- cantina
- tractors are late
- intraMode: 1 allows for a single error in each term of the search phrase, where an error is one of: substitution (replacement), transposition (swap), insertion (addition), or deletion (omission). The search strings with errors below can return matches containing "example". What is actually matched will depend on additonal fuzziness settings. In contrast to the previous mode, searching for "example" will never match "extra maple".
example- exactexamplle- single insertion (addition)exemple- single substitution (replacement)exmaple- single transposition (swap)exmple- single deletion (omission)xamp- partialxmap- partial with transposition
There are 3 phases to a search:
- Filter filters the full
haystackwith a fast RegExp compiled from yourneedlewithout doing any extra ops. It returns an array of matched indices in original order. - Info collects more detailed stats about the filtered matches, such as start offsets, fuzz level, prefix/suffix counters, etc. It also gathers substring match positions for range highlighting. Finally, it filters out any matches that don't conform to the desired prefix/suffix rules. To do all this it re-compiles the
needleinto two more-expensive RegExps that can partition each match. Therefore, it should be run on a reduced subset of the haystack, usually returned by the Filter phase. The uFuzzy demo is gated at <= 1,000 filtered items, before moving ahead with this phase. - Sort does an
Array.sort()to determine final result order, utilizing theinfoobject returned from the previous phase. A custom sort function can be provided via a uFuzzy option:{sort: (info, haystack, needle) => idxsOrder}.
A liberally-commented 100 LoC uFuzzy.d.ts file.
Options with an inter prefix apply to allowances in between search terms, while those with an intra prefix apply to allowances within each search term.
| Option | Description | Default | Examples |
|---|---|---|---|
intraMode |
How term matching should be performed | 0 |
0 MultiInsert1 SingleErrorSee How It Works |
intraIns |
Max number of extra chars allowed between each char within a term |
0 |
Searching "cat"...0 can match: cat, scat, catch, vacate1 also matches: cart, chapter, outcast |
interIns |
Max number of extra chars allowed between terms | Infinity |
Searching "where is"...Infinity can match: where is, where have blah wisdom5 cannot match: where have blah wisdom |
intraSubintraTrnintraDel |
For intraMode: 1 only,Error types to tolerate within terms |
0 |
0 No1 Yes |
intraChars |
Partial regexp for allowed insert chars between each char within a term |
[a-z\d] |
[a-z\d] matches only alpha-numeric (case-insensitive)[\w-] would match alpha-numeric, undercore, and hyphen |
intraFilt |
Callback for excluding results based on term & match | (term, match, index) => true |
Do your own thing, maybe...
- Length diff threshold - Levenshtein distance - Term offset or content |
interChars |
Partial regexp for allowed chars between terms | . |
. matches all chars[^a-z\d] would only match whitespace and punctuation |
interLft |
Determines allowable term left boundary | 0 |
Searching "mania"...0 any - anywhere: romanian1 loose - whitespace, punctuation, alpha-num, case-change transitions: TrackMania, maniac2 strict - whitespace, punctuation: maniacally |
interRgt |
Determines allowable term right boundary | 0 |
Searching "mania"...0 any - anywhere: romanian1 loose - whitespace, punctuation, alpha-num, case-change transitions: ManiaStar2 strict - whitespace, punctuation: mania_foo |
sort |
Custom result sorting function | (info, haystack, needle) => idxsOrder |
Default: Search sort, prioritizes full term matches and char density Demo: Typeahead sort, prioritizes start offset and match length |
This assessment is extremely narrow and, of course, biased towards my use cases, text corpus, and my complete expertise in operating my own library. It is highly probable that I'm not taking full advantage of some feature in other libraries that may significantly improve outcomes along some axis; I welcome improvement PRs from anyone with deeper library knowledge than afforded by my hasty 10min skim over any "Basic usage" example and README doc.
Can-of-worms #1.
Before we discuss performance let's talk about search quality, because speed is irrelevant when your results are a strange medly of "Oh yeah!" and "WTF?".
Search quality is very subjective. What constitutes a good top match in a "typeahead / auto-suggest" case can be a poor match in a "search / find-all" scenario. Some solutions optimize for the latter, some for the former. It's common to find knobs that skew the results in either direction, but these are often by-feel and imperfect, being little more than a proxy to producing a single, composite match "score".
Let's take a look at some matches produced by the most popular fuzzy search library, Fuse.js and some others for which match highlighting is implemented in the demo.
Searching for the partial term "twili", we see these results appearing above numerous obvious "twilight" results:
- twirling
- The total number of received alerts that were invalid.
- Tom Clancy's Ghost Recon Wildlands - ASIA Pre-order Standard Uplay Activation
- theHunter™: Call of the Wild - Bearclaw Lite CB-60
Not only are these poor matches in isolation, but they actually rank higher than literal substrings.
Finishing the search term to "twilight", still scores bizzare results higher:
- Magic: The Gathering - Duels of the Planeswalkers Wings of Light Unlock
- The Wild Eight
Some engines do better with partial prefix matches, at the expense of higher startup/indexing cost:
Here, match-sorter returns 1,384 results, but only the first 40 are relevant. How do we know where the cut-off is?
Can-of-worms #2.
All benchmarks suck, but this one might suck more than others.
- I've tried to follow any "best performance" advice when I could find it in each library's docs, but it's a certainty that some stones were left unturned when implementing ~20 different search engines.
- Despite my best efforts, result quality is still extremely variable between libraries, and even between search terms. In some cases, results are very poor but the library is very fast; in other cases, the results are better, but the library is quite slow. What use is extreme speed when the search quality is sub-par? This is a subjective, nuanced topic that will surely affect how you interpret these numbers. I consider uFuzzy's search quality second-to-none, so my view of most faster libraries is typically one of quality trade-offs I'm happy not to have made. I encourage you to evaluate the results for all benched search phrases manually to decide this for yourself.
- Many fulltext & document-search libraries compared here are designed to work best with exact terms rather than partial matches (which this benchmark is skewed towards).
Still, something is better than a hand-wavy YMMV/do-it-yourself dismissal and certainly better than nothing.
- Each benchmark can be run by changing the
libsparameter to the desired library name: https://leeoniya.github.io/uFuzzy/demos/compare.html?bench&libs=uFuzzy - Results output is suppressed in
benchmode to avoid benchmarking the DOM. - Measurements are taken in the Performance secrion of Chrome's DevTools by recording several reloads of the bench page, with forced garbage collection in between. The middle/typical run is used to collect numbers.
- The search corpus is 162,000 words and phrases, loaded from a 4MB testdata.json.
- The benchmark types and then deletes, character-by-character (every 100ms) the following search terms, triggering a search for each keypress:
test,chest,super ma,mania,puzz,prom rem stor,twil.
To evaluate the results for each library, or to compare several, simply visit the same page with more libs and without bench: https://leeoniya.github.io/uFuzzy/demos/compare.html?libs=uFuzzy,fuzzysort,QuickScore,Fuse&search=super%20ma.
There are several metrics evaluated:
- Init time - how long it takes to load the library and build any required index to perform searching.
- Bench runtime - how long it takes to execute all searches.
- Memory required - peak JS heap size used during the bench as well as how much is still retained after a forced garbage collection at the end.
- GC cost - how much time is needed to collect garbage at the end (main thread jank)
| Lib | Stars | Size (min) | Init | Search | Heap (peak) | Retained | GC |
|---|---|---|---|---|---|---|---|
| uFuzzy (try) | ★ 0 | 4KB | 0.3ms | 630ms | 25.5MB | 7.5MB | 20ms |
| Fuse.js (try) | ★ 14.8k | 23.5KB | 40ms | 35600ms | 323MB | 14.5MB | 30ms |
| FlexSearch (Light) (try) | ★ 8.9k | 5.9KB | 3600ms | 130ms | 673MB | 316MB | 320ms |
| Lunr.js (try) | ★ 8.2k | 29.4KB | 2000ms | 800ms | 355MB | 121MB | 130ms |
| LyraSearch (try) | ★ 3.3k | ||||||
| match-sorter (try) | ★ 3.1k | 7.3KB | 0.03ms | 10000ms | 79MB | 8MB | 30ms |
| fuzzysort (try) | ★ 3k | 5.5KB | 60ms | 1500ms | 176MB | 84MB | 70ms |
| Wade (try) | ★ 3k | 4KB | 840ms | 370ms | 436MB | 42MB | 100ms |
| fuzzysearch (try) | ★ 2.6k | ||||||
| js-search (try) | ★ 2k | 17.1KB | 6500ms | 1350ms | 1937MB | 734MB | 1400ms |
| Elasticlunr.js (try) | ★ 1.9k | 18.1KB | 1220ms | 1770ms | 238MB | 70MB | 100ms |
| MiniSearch (try) | ★ 1.5k | 22.4KB | 525ms | 1800ms | 422MB | 64MB | 90ms |
| Fuzzyset (try) | ★ 1.3k | 2.8KB | 3500ms | 1000ms | 660MB | 238MB | 430ms |
| search-index (try) | ★ 1.3k | ||||||
| LiquidMetal (try) | ★ 285 | ||||||
| ItemJS (try) | ★ 260 | ||||||
| FuzzySearch (try) | ★ 184 | ||||||
| FuzzySearch2 (try) | ★ 173 | ||||||
| QuickScore (try) | ★ 131 | 9.1KB | 40ms | 7500ms | 176MB | 12.8MB | 30ms |
| fzy (try) | ★ 115 | ||||||
| fuzzyMatch (try) | ★ 0 |