3 ms·
> The benchmark was very simple. A single-shard point select, one row fetched per-query by primary key. No writes, joins, or cross-shard queries. The workload t
by _zoltan_ 22d ago
> The benchmark was very simple. A single-shard point select, one row fetched per-query by primary key. No writes, joins, or cross-shard queries. The workload that each shard receives is isolated, in that there are no single queries that span multiple shards.
I mean... What's the point of this "benchmark"?
- voodoo_child 20d ago> Worth being clear about this run: the shards were primary-only with no replicas, the workload is read-only across queries ranging in complexity, and we did not fail over during the measured window. No HA either, or backups I assume.(single AZ?) But think the point of it was not to benchmark PostgreSQL but to demonstrate the linear scalability of the shared-nothing/stateless routing architecture. I think this was already known from Vitess though, which shares the same architecture. Also, as part of a new product release benchmarking shit like this internally is cool/interesting, why not blog about it. The more cynical side of me says it was a money burning exercise to give the marketing team a number to tweet about. :)