Viewing profile — _peregrine_

this is actually not how cursor uses turbopuffer, as they index per codebase and thus need many mid-sizes indexes as opposed to one massive index as this post describes

unfortunately i'm not able to share the customer or use case :( but the metrics that you see in the first charts in the post are from a production cluster

the solution described in the blog post is currently in production at 100B vectors

seems like a good rule of thumb to me! though i would perhaps lump "cost" into the "until it breaks" equation. even with decent perf, pg_vector's economics can be much worse, espec…

yeah I mean that's basically what Javi talks about in the post... if you can throw hardware at it you can scale it (ingestion scales linearly with shards) but the post has some int…

definitely interesting and related

nice one

Pretty solid at SQL generation, too. Just tested in our generation benchmark: https://llm-benchmark.tinybird.live/ Not quite as good as Claude but by the best Qwen model so far and…

Yeah we're always looking for new models to add

Yeah I mean SQL is pretty nuanced - one of the things we want to improve in the benchmark is how we measure "success", in the sense that multiple correct SQL results can look struc…