3 ms·
Ask HN: What is the biggest database you’ve worked with in MySQL / PostgreSQL?
And how well did it perform / what issues did you run into?
- ta1664243775619 4y agoClient explored moving 200TB (two hundred terabyte) Oracle Exadata database to Postgres. I was part of a team that tried all manner of sharding and partitioning. Could not meet the benchmark set by the Exadata instance. Can kicked down the road five years.
- altdataseller 4y agoTheres a reason why Oracle is still a dominant “legacy” database.
- thorin 4y agoThere are plenty of reasons, a DBA I used to work with moved to the team running the LHC at CERN. I think I went to some conference talks of his. They had a lot of data!
- herodoturtle 4y agoHey thanks for the comment. By “benchmark” do you mean throughput? Or just the ability to store the data in general? I’m trying to get a real world sense of what’s possible with these databases at scale.
- palashkulsh 4y ago
- sethammons 4y agoAt my last gig, one of our services was backed by mysql had a table that was sharded (so, actually many tables) and partitioned so data would fall off after N days. Each table was a couple hundred gigabytes, couple hundred million rows. One writer, and three readers. Our biggest problem was that our public api could delete and/or bulk delete data out of these tables, causing locking issues for other clients and services that needed responses from the same tables. We played around with different ways to manage it from the db side but ended up just needing to change the public API to return 202 "will delete later" and then we could smooth the load over time.