4 ms·
> Weird pricing: PlanetScale prices you on row-reads and row-writes per month. What is weird is that row-reads is something that nobody controls. It is the SQL
by mijoharas 3y ago
> Weird pricing: PlanetScale prices you on row-reads and row-writes per month. What is weird is that row-reads is something that nobody controls. It is the SQL query planner which determines the query plan, which results in how many rows you’re reading internally. Remember that row-reads are not row returns. You can write a wrong query that returns 0 rows but can still do a full table scan of 1M rows and PlanetScale will charge you for it.
Followed by:
> AWS Aurora Serverless v2 Postgres
I hope they don't get an unpleasant shock when they see the IO pricing on their aurora bill (it's per block read/write rather than per row, but that's proportional in the random access case, and you're also beholden to the query planner, so basically the same).
- reedf1 3y agoWhat do they think is executing the table scan? Do they think that the underlying hardware should be free?
- eightnoteight 3y agoaurora serverless v2 now supports io optimized mode. which increases the pricing for instances by constant amount but makes the io pricing to 0 https://aws.amazon.com/about-aws/whats-new/2023/05/amazon-aurora-i-o-optimized/ https://aws.amazon.com/about-aws/whats-new/2023/05/amazon-au...
- mijoharas 3y agoOh, very cool!
- naiv 3y agoI also think that this is the old Planetscale pricing. The new one has unlimited reads (https://planetscale.com/pricing https://planetscale.com/pricing)
- patmorgan23 3y agoRow-reads sounds like a perfectly acceptable metric to use for billing. It's basically changing based on disk io. So what if the result of your query is 0, the server has to do a bunch of work to figure out the answer is 0.
- zaphirplane 3y agoWhat about indexes, should ppl add a ton of indexes to optimize the query cost