Thanks for repost the blog! Some crazy guys have already told me that they have mysql table >1.4B rows (~180GiB), underestimated mysql's power lol
Is 20M of rows still a valid soft limit of MySQL table in 2023?
11–20 of 86 posts
Re: Is 20M of rows still a valid soft limit of MySQL table in 2023?
#12Re: Is 20M of rows still a valid soft limit of MySQL table in 2023?
#13Earlier quoted context omitted.
Agreed. I have a handful of tables with over 2 billion rows and have experienced no issues. One database is 2.5TB in size. I feel like 20 million rows is a relatively small MySQL table.
What types of data with over two billion rows?
Re: Is 20M of rows still a valid soft limit of MySQL table in 2023?
#14Earlier quoted context omitted.
My current employer has a single InnoDB table that is 14-15 TB.
what is it?
The system design predates me, but it is solid (albeit difficult to operate at this scale - usual stuff like schema changes, replication bootstrapping).
Re: Is 20M of rows still a valid soft limit of MySQL table in 2023?
#15...yes, performance will drop when your set of active data exceeds available memory and your system needs to reference slower storage. I assume this would apply to anything.
Re: Is 20M of rows still a valid soft limit of MySQL table in 2023?
#16You can safely go to a billion rows. Use indexes. Don't do silly things like count(*) or select *, select the small data sets you need using your indexes. If you need a full table count for some reason, use a primary key that auto increments and select the max, or use information_schema for an estimate. Nobody will sweat the slight inaccuracy on a table that size.
Agreed. I have a handful of tables with over 2 billion rows and have experienced no issues. One database is 2.5TB in size. I feel like 20 million rows is a relatively small MySQL table.
Re: Is 20M of rows still a valid soft limit of MySQL table in 2023?
#17Re: Is 20M of rows still a valid soft limit of MySQL table in 2023?
#18Earlier quoted context omitted.
what is it?
Events that are enriched off of other data in the same DB. The system design predates me, but it is solid (albeit difficult to operate at this scale - usual stuff like schema changes, replication bootstrapping).