leentee

3 ms·

1. 1.▲
   by leentee 3mo ago

   What I get from this is frontier model capabilities are being stagnant.
2. 2.▲
   by leentee 6mo ago

   Look at their benchmark charts to understand how desperate they're. A lame duck now.
3. 3.▲
   by leentee 9mo ago

   From my experience optimizing an OLAP database with high concurrency; lots of time the bottleneck is memory speed.
4. 4.▲
   by leentee 1y ago

   No backup, no replica? Such a shame.
5. 5.▲
   by leentee 1y ago

   I think the new UPDATE implementation is great, however its impact is limited. As a heavy CH user, our typical use case is inserting rows with some columns are missing, then backfill these columns later on (and I've seen such pattern i
6. 6.▲
   by leentee 1y ago

   First, I think the article provides false claim, the solution doesn't guarantee durability. Second, I believe good synchronous code is better than bad asynchronous code, and it's way easier to write good synchronous code than asy
7. 7.▲
   by leentee 3y ago

   Yet another database built on ByteKV. Back then when I was in ByteDance, all infrastructure were more or less using ByteKV for data and metadata storage. Unfortunately we had less information about this technology because dev are in China (
8. 8.▲
   by leentee 3y ago

   I believe the author means "the best transactional k/v store"