3 ms·
I'm often using Fuse in my JS apps. So many in-app searchs cannot handle typing errors, it's frustrating.
by maelito 2y ago
I'm often using Fuse in my JS apps. So many in-app searchs cannot handle typing errors, it's frustrating.
- efilife 2y agoFuse is terrible performance-wise. There are many better options https://github.com/nextapps-de/flexsearch?tab=readme-ov-file#performance-benchmark-ranking https://github.com/nextapps-de/flexsearch?tab=readme-ov-file... I tried Fuse, lunr and MiniSearch, and I stayed with MiniSearch. Great flexibility and very good performance even when I am indexing almost a million documents + many useful features. Also, I would also recommend giving FlexSearch a try, it has some fancy algorithm that supposedly makes searches extra fast https://github.com/nextapps-de/flexsearch?tab=readme-ov-file#contextual-search https://github.com/nextapps-de/flexsearch?tab=readme-ov-file...
- leeoniya 2y agoyes, Fuse is extremely slow (and FlexSearch is very fast after indexing is done), but i have no idea how that table presents FlexSearch as having the lowest memory footprint, maybe in its default config? in my testing of fuzzy/substring matching it takes quite a while to create its huge index: https://github.com/leeoniya/uFuzzy?tab=readme-ov-file#performance https://github.com/leeoniya/uFuzzy?tab=readme-ov-file#perfor...