Turbopuffer: Fast search on object storage

Having worked with Simon he knows his sh*t. We talked a lot about what the ideal search stack would look when we worked together at Shopify on search (him more infra, me more ML+relevance). I discussed how I just want a thing in the cloud to provide my retrieval arms, let me express ranking in a fluent &quot;py-data&quot; first way, and get out of my way<p>My ideal is that turbopuffer ultimately is like a Polars dataframe where all my ranking is expressed in my search API. I could just lazily express some lexical or embedding similarity, boost with various attributes like, maybe by recency, popularity, etc to get a first pass (again all just with dataframe math). Then compute features for a reranking model I run on my side - dataframe math - and it &quot;just works&quot; - runs all this as some kind of query execution DAG - and stays out of my way.

Unrelated to the core topic, I really enjoy the aesthetic of their website. Another similar one is from Fixie.ai (also, interestingly, one of their customers).

&gt; $3600.00&#x2F;TB&#x2F;month<p>It doesn&#x27;t have to be that way.<p>At Hetzner I pay $200&#x2F;TB&#x2F;month for RAM. That&#x27;s 18x cheaper.<p>Sometimes you can reach the goal faster with less complexity by removing the part with the 20x markup.

&gt; In 2022, production-grade vector databases were relying on in-memory storage<p>This is irking me. pg_vector has existed from before that, doesn&#x27;t require in-memory storage and can definitely handle vector search for 100m+ documents in a decently performant manner. Did they have a particular requirement somewhere?

Sounds like a source-unavailable version of Quickwit? <a href="https:&#x2F;&#x2F;quickwit.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;quickwit.io&#x2F;</a>

Is there a good general purpose solution where I can store a large read only database in s3 or something and do lookups directly on it?<p>Duckdb can open parquet files over http and query them but I found it to trigger a lot of small requests reading bunch of places from the files. I mean a lot.<p>I mostly need key &#x2F; value lookups and could potentially store each key in a seperate object in s3 but for a couple hundred million objects.. It would be a lot more managable to have a single file and maybe a cacheable index.

Is it feasible to try to build this kind of approach (hot SSD cache nodes sitting in front of object storage) with prior open-source art (Lucene)? Or are the search indexes themselves also proprietary in this solution?<p>Having witnessed some very large Elasticsearch production deployments, being able to throw everything into S3 would be <i>incredible</i>. The applicability here isn&#x27;t only for vector search.

A correction to the article. It mentions<p><pre><code> Warehouse BigQuery, Snowflake, Clickhouse ≥1s Minutes </code></pre> For ClickHouse, it should be: read latency &lt;= 100ms, write latency &lt;= 1s.<p>Logging, real-time analytics, and RAG are also suitable for ClickHouse.

I love the object-storage-first approach; it seems like such a natural fit for the could.

The very long introductory page has a ton of very juicy data in it, even if you don&#x27;t care about the product itself.

This looks super interesting. I&#x27;m not that familiar with vector databases. I thought they were mostly something used for RAG and other AI-related stuff.<p>Seems like a topic I need to delive into a bit more.

Slightly relevant - do people really want article recommendations? I don’t think I’ve ever read an article and wanted a recommendation. Even with this one - I sort of read it and that’s it; no feeling of wanting recommendations.<p>Am I alone in this?<p>In any case this seems like a pretty interesting approach. Reminds me of Warpstream which does something similar with S3 to replace Kafka.

Sounds like a filesystem with attributes in a database.

can&#x27;t wait for the day the get into GA!

Can you compare to S3 Athena (ELI5)?

unsure if they are comparable, but is this and quickwit comparable?

That’s some woefully disappointing and incorrect metrics (read and write latency are both sub-second, storage medium would be “ Memory + Replicated SSDs”) you’ve got for Clickhouse there, but I understand what you’re going for and why you categorized it where you did.