jamesgresql

This is our old pitch, we have our own vector data-type in our main index in beta.

pg_search does both vector (this) and full-text (bm25) in a single index.

ParadeDB'er here: We are really hoping this can turn into a back and forth, making both of our products better.

ParadeDB built a benchmark runner to make experimentation easy. This post looks at a real example over three iterations (with wildly different results).

We (ParadeDB) recently started building out our benchmarking infrastructure for cross-backend comparisons.

Rather than taking the usual path of bundling a workload and execution into one neat package, we decided to build a reusable database benchmark runner based on grafana/k6 first.

This is great, no more lost terminal screens!

"If I had looked at the lexical search and BM25 space in 2016, I would have said it was solved, and that catching up would be nearly impossible."

This interview with Tantivy creator Paul Masurel looks at how wrong I would have been; discussing challenging solved domains, open-source competition done right, and why long-fermented frustration is an underrated driver.

Yeah I get that, I threw caution to the wind and did it (which I would normally never dO)

I have no affiliation with this product other than being a happy user, but man is it good for finding out exactly why and when your wifi is slow.

Best feature for me being was being able to detect intermittent jitter to my gateway. I never managed to catch this with speed-tests alone.