Recent submissions

Comment · 16 minutes ago
I have a hard time believing that this is some sort of emergent behavior and not the result of intentional training to scale AI research.
Comment · 10 hours ago
I commend Orkes for funding a Jepsen report knowing that it could be published this harshly. I question the wisdom of doing so, but it at least speaks to the team's integrity. Building databases is very hard; I know this from personal experience.

Disclosure: I'm a software engineer on the core team at a different database company, but we focus on time-series use cases and do not compete in the ACID/OLTP space ParticleDB is targeting.

I decided to dig into these claims a bit.

> Its also faster than Redis for KV

ParticleDB's own benchmarks[0] come with several caveats. Much of the win over Redis seems to come from comparing ParticleDB on 48 cores to Redis's single execution thread, from what I can tell.

- On a single client in async mode, ParticleDB loses on writes at 0.86-0.90x and ties on GET.

- SET at 512 clients reaches 4.81x Redis, but that's about 18.7k ops/s per allocated core vs Redis's 186k on one thread. For comparison, GET at 512 clients works out to about 33.8k ops/s per allocated core vs Redis's 228k.

- Tail latency on SET is much worse, e.g. p99 of 49ms vs 5.3ms for async SET at 512 clients and 306ms vs 41ms for durable mode with pipelining.

- Each test was 8 seconds long on 100k keys, but the Jepsen report saw throughput decline linearly over an hour, even on small datasets.

> also numbers show this should be top on clickbench

Would this claim survive after validating query results?

Regardless, it's moot, because it doesn't survive on its face either. On hot runs, by my calculations from the numbers in the Clickbench PR[1], ParticleDB scores about 1.5x better than ClickHouse, however Umbra still scores about 1.5x better than ParticleDB.

The fact that `GROUP BY URL` (Q33/Q34) beats `GROUP BY UserID` (Q15) by 4x on a `c6a` is also puzzling to me. Only a handful of 100+ ClickBench results that I checked do this, and ParticleDB's ratio is the most extreme. It also speeds up only 2.2x when going from 16 to 192 vCPUs, while Umbra, ClickHouse, and ElosDB manage 7-10x. This makes me wonder whether the ParticleDB submission may inadvertently be using some precomputation/intermediate caching, despite final result caching seemingly having been disabled.

[0]: https://particledb.ai/benchmarks/key-value/

[1]: https://github.com/ClickHouse/ClickBench/pull/2952

Comment · 12 hours ago
*VS Code extension for Claude Code
Comment · 2 days ago
I rented a hetzner server years ago and have steadily grown into it. No increasing costs so far.
Comment · 4 days ago
Very wise of you to keep MIL receipts. You never know when you might need them...
Comment · 9 days ago
I don't think anything compares to Anthropic's plans. You still won't get much mileage out of the $20 plan, but it feels like it's 5x as much as other $20 plans.

The Max 20x plan is incredible value. I am able to burn something like $2k in tokens each week without consuming any credits.

Comment · 13 days ago
Comment · 14 days ago
He isn't playing on live servers. He is running a 2004scape private server, a project which Jagex has blessed.
Comment · 15 days ago
Monitorability and safety, no? This results in lower volume or less accurate text reasoning traces, right?
Comment · 15 days ago
Ah, the classic economists and GDP joke.
Comment · 22 days ago
Basically an EZ-Pass.
Comment · 26 days ago
Usually only the story gets ported.
Comment · 1 month ago
Obscurity is a valuable layer of defense-in-depth
Comment · 1 month ago
Stateful Kubernetes is a royal PITA. I would just throw stage into object storage and call it a day.
Comment · 1 month ago
OpenAI is cutting their subscription's token value in half. Half. I don't think this is enough to help them compete with Opus 5.5.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton