tinysearch VS pagefind

When getting into performance territory you might want to work on the performance of the index, there are multiple options, you could implement fuse filters or Bloom Filters or XOR Filters like the ones suggested in the blog post. If you want to go for a further performance bump, server side is your best bet.

If your content is mostly static, you might want to consider pre-building an index and shipping it as a whole. You could look into something like

* https://stork-search.net/ (Rust/WASM)

* tinysearch: https://github.com/tinysearch/tinysearch (Rust/WASM)

* https://lunrjs.com/ (JS, simple, stable)

* http://elasticlunr.com/ - based on the former, slightly more sophisticated tuning options

500kB sounds, like could be just shipped to the client lazily? https://github.com/tinysearch/tinysearch

Checkout https://github.com/mre/tinysearch

Pagefind is a static search library that aims to perform well on small or large sites, while using as little bandwidth as possible, and you don't have to host any infrastructure.

In theory, if we ran lower level code, we would be using less resources. That's more than a theory. Go to this video where I demonstrate Pagefind, written in Rust and compiled to Wasm as target, as a static app that ingests and indexes HTML documents and runs super efficient search queries, all client-side.

✅ Pagefind static search library integration

I use Astro SSG and Cloudflare Pages. I use https://github.com/cloudcannon/pagefind for search on my Astro setup. You can test the search functionality here https://tinyrocket.pages.dev/.

From its repo: "Pagefind runs after any static site generator and automatically indexes the built static files. Pagefind then outputs a static search bundle to your website, and exposes a JavaScript search API that can be used anywhere on your site."

Pagefind is cool!

An option there is https://pagefind.app/ — not as fast as a persistent server but solves some of the deployment and bandwidth issues.