3 ms·
I have more experience running large MySQL databases. Both at SurveyMonkey and Zapier our primary databases were MySQL and were massive as you can imagine fro
by sontek 3y ago
I have more experience running large MySQL databases. Both at SurveyMonkey and Zapier our primary databases were MySQL and were massive as you can imagine from massively scaled consumer products. I won't list the data here since this is about postgres but wanted to provide the context.
The largest postgres I've personally administered is on RDS:
* postgres 13.4
* db.m6g.2xlarge (8vCPU, 32 GB RAM)
* 1.3tb storage
* Largest tables: 317GB, 144GB, and 142GB
I effectively treat this database as an analytics database and write massive queries with joins against those largest tables and postgres handles it just fine.
I have had random bad query plans when using CTEs that get cached and take down the entire DB for a bit but usually been able to fix it with `vacuum analyze` and the customizing the query to convince postgres to choose a better plan.
Overall I think postgres can do a lot of work with very little.
- okl 3y agoFor me, your numbers underline the "premature optimization is the root of all evil" saying. Maybe misunderstanding the performance implications of different orders of mangitudes is similar to the lack of understanding in statistics. I often encounter colleagues or customers who worry about some data structure or table when there are 10s of thousands of entries which is actually not enough to spend that much time worrying about.
- jjice 3y agoOut of curiosity, were those CTE issues on the current PG version (13.4)? I know they changed some materialization stuff with them in 12 or so but was wondering if that issue was from back then or if you're running into some stuff that currently still happens.
- stocktech 3y agoWhen you say 'analytics database', what kind of performance are you implying? Massive queries that respond in 10min? How tuned were things for the queries you were running? I'm currently working through an analytics architecture and I'm having to defend against "why aren't you using postgres" when I'm talking about olap dbs.
- flerovium 3y agoPlease share the details of the MySQL ones! I said "postgres" because I didn't want to say "SQL" and include crazy systems with SQL query interfaces.