4 ms·

I wonder how this compares to Flexsearch or the other benchmarked libraries here: https://github.com/nextapps-de/flexsearch#performance-benchmark-ranking https:

• micheleriva 4y ago
  Lyra author here: I wouldn't compare it with other JS search engines for a simple reason: we'll be targeting edge execution (Cloudflare workers, lambda@edge, etc.), so the focus is really different
  • kasbah 4y ago
    Why does that matter? It seems you can run Lyra on the client and you can run other JS search engines on the "edge" (all that's needed is a JS runtime if I understand it correctly). It would be interesting to see how Lyra compares in these benchmarks.
    • micheleriva 4y ago
      We have a benchmark section in the repo and it's performing pretty well, we'll definitely run it against other engines!
• somishere 4y ago
  I quite enjoy minisearch[1] which is also 0 dependencies, actively maintained, and I expect would work well in a worker environment. I dropped it into a service worker and plugged it with a simple point in polygon script to enable geosearch for a recent project[2] and it played v. nicely. [1] https://github.com/lucaong/minisearch https://github.com/lucaong/minisearch [2] https://github.com/theprojectsomething/re.places https://github.com/theprojectsomething/re.places
• alessmar 4y ago
  Current version of FlexSearch (0.7.2) is not typo tolerant, see https://github.com/nextapps-de/flexsearch/issues/118 https://github.com/nextapps-de/flexsearch/issues/118