nvanbenschoten

3 ms·

1.
by nvanbenschoten 8mo ago
(author here) The 92% mentioned in this post is showing recall@10 across all 100B vectors, calculated by comparing to the global top_k. turbopuffer will also continuously monitor production recall at the per-shard level (or on-demand with
2.
by nvanbenschoten 3y ago
> Cockroach only allow SERIALIZABLE transactions so the unviability of SERIALIZABLE seems questionable. We've actually been hard at work on adding Read Committed and Repeatable Read isolation into CockroachDB. The risks of weak isol
3.
by nvanbenschoten 4y ago
I don't think this scheme provides the "monotonic reads" property discussed in the blog post. Specifically, it would be possible for a reader to observe a new value from r2 (who received a timely heartbeat), then to later obs
4.
by nvanbenschoten 6y ago
Hi cuu508, CockroachDB engineer here. You are correct that row-level partitioning is not supported in the OSS version of CRDB. However, it sounds like there's a bit of confusion about where manual table partitioning is and is not neede
5.
by nvanbenschoten 7y ago
> If it's PENDING, reader just ignores it and skips its data, since they use MVCC. There's no waiting here. I think this is where the confusion is coming from. You're correct that a read can simply ignore writes, even pend
6.
Pipelining Consensus Writes to Speed Up Distributed SQL Transactions(cockroachlabs.com)
85 points by nvanbenschoten 8y ago|1 comments
7.
Executing Parallel Statements to Improve Performance(cockroachlabs.com)
53 points by nvanbenschoten 9y ago|14 comments
8.
Revisiting SQL typing in CockroachDB(cockroachlabs.com)
9 points by nvanbenschoten 10y ago|0 comments