Pinned
PlanetScale
@PlanetScale
The fastest and most reliable database for Postgres & Vitess
Discord: pscale.link/community
Support: @planetscalehelp
planetscalestatus.com
Joined February 2018
- A Postgres transaction opens 65 subtransactions. The result? 7,200 TPS → 160 TPS performance drop. We dive deep into Postgres internals in our latest blog, showing why this happens and the dangers of using too many subtransactions in Postgres.
- Reduce parallelism. Increase throughput. Sounds backwards, but past a certain point, each additional in-flight query can make all the others slower. We recently observed this in a customer's Vitess database. How it happened, and the fix:
- One of the hardest parts of sharding databases? Query planning. Here's why it's so complex to handle on your own, and why you want Neki and Vitess to make it scale 📈
- Less than a week until @CanadaHonk's Porffor JS runtime launch hosted at PlanetScale HQ. Make sure you RSVP!
