Oct 25, 2026 · 16 min · 9 segments
In this episode of Scaling Postgres, we discuss how to reach 10 million queries per second efficiently, Postgres performance on GPUs, the next release of pgrust and not trusting ON DELETE CASCADE. To…
Creston JamisonHost
Our first piece of content is Open Source Citus Matches Planet Scales NICKEY at 10 Million Queries Per Second on Half the Data Nodes.

This is from stackgres.io. And looking at the graph here, they achieved 10 million queries per second, which is what PlanetScale's Neki did on 50 nodes, and Stackgres's open source implementation of Citus, where they're using a query router pattern that they developed to achieve 10 million queries per second on 24 data nodes, so less machines.

And the blog post starts off, you know, last month PlanetScale published a blog post on how they achieved 118 million queries per second on Neki, but they included data points at 5 data nodes, 50 data nodes, and 512 shards.

So basically they attempted to match their 50 node test And you'll see why in a second.

And this is a follow-on blog post from the one we covered last week where they talked about their query routers they developed to work with Citus.

And as opposed to sending all traffic through the Citus coordinator node, you send them through query routers and you get close to linear scalability of your query traffic.

And with three query nodes and three data nodes, I believe they got up to 1.4 million queries per second.

And so they went ahead and they matched the 1 million and 10 million data points.

Now, this wasn't doing writes, it was just doing reads, and there were single row primary key reads to match what Nikki was doing, presumably.

There were primaries only, which I remember, that's what Nikki did, no replicas.

That means the one that StackRes used was using local NVMe disks instead of network storage.

But I thought PlanetScale was known for their bare metal, so it's interesting that they use these.

So for this test, it looks like they have three worker nodes, which is basically where the data is stored, sharded.

And basically they were able to get up to 10 million transactions per second from almost 20,000 clients sending traffic to it.

Our first piece of content is Open Source Citus Matches Planet Scales NICKEY at 10 Million Queries Per Second on Half the Data Nodes.

This is from stackgres.io. And looking at the graph here, they achieved 10 million queries per second, which is what PlanetScale's Neki did on 50 nodes, and Stackgres's open source implementation of Citus, where they're using a query router pattern that they developed to achieve 10 million queries per second on 24 data nodes, so less machines.

And the blog post starts off, you know, last month PlanetScale published a blog post on how they achieved 118 million queries per second on Neki, but they included data points at 5 data nodes, 50 data nodes, and 512 shards.

So basically they attempted to match their 50 node test And you'll see why in a second.

And this is a follow-on blog post from the one we covered last week where they talked about their query routers they developed to work with Citus.

And as opposed to sending all traffic through the Citus coordinator node, you send them through query routers and you get close to linear scalability of your query traffic.

And with three query nodes and three data nodes, I believe they got up to 1.4 million queries per second.

And so they went ahead and they matched the 1 million and 10 million data points.

Now, this wasn't doing writes, it was just doing reads, and there were single row primary key reads to match what Nikki was doing, presumably.

There were primaries only, which I remember, that's what Nikki did, no replicas.

That means the one that StackRes used was using local NVMe disks instead of network storage.

But I thought PlanetScale was known for their bare metal, so it's interesting that they use these.

So for this test, it looks like they have three worker nodes, which is basically where the data is stored, sharded.

And basically they were able to get up to 10 million transactions per second from almost 20,000 clients sending traffic to it.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.