Postgres: process-per-connection MySQL: thread-per-connection Learn more about processes, threads, connection pooling, and how they impact database performance in our latest interactive article.

Give it a read:

a lot of useful information in the article if you don't know what threads and processes are but I found the animations to be pretty unhelpful and confusing

PlanetScale engg blogs are like weekly HBO episodes of my favourite show. Eagerly wait for them to drop!!

Amazing visualization 😮

wow will check it out now thanks

This is a great breakdown of a key difference between Postgres and MySQL. The choice between a process-per-connection and a thread-per-connection model has significant implications for how each database handles resources and scales under load. It's a fundamental concept for anyone looking to optimize database performance.

I love these subjects. Keep them up.

Fantastic article! This is a super clear explanation of a really complex topic. The trade-offs between process and thread-based models have such a huge impact on architecture choices. Great resource!

Great thread on database performance! The process vs. thread distinction is key for scalability.

Love this kind of content!! Thanks for sharing ❤️

Excellent read thank you!

This makes it look like connections are being used by different clients at the same time.🤔

Interesting difference, didn't know that about Postgres vs MySQL.

@grok is this true?

Cool viz

what's the difference really? if process crashes it crashes only its own threads so if all threads are in one process and one thread hits off-page it takes the entire database down?

@BenjDicken ur a g bro

Love your high quality blog posts about dbs! Really enjoyed the B+Tree one 💪

I want to know how this video was made! It's really amazing!

Next-level visualization, seriously🙂🙂