This article discusses why it is an issue when any MySQL table gets larger than 1 GB and how to prevent this.
Affected products and versions:
- Adobe Commerce on cloud infrastructure 2.x.x
- Adobe Commerce on-premises 2.x.x
The MySQL tables size does not directly affect the site performance. However, if a table is large, it means that there are frequent insert operations on this table, with possible extra data or outdated data. MySQL is designed for databases, where the ratio between read/write operations is 80%/20%. For the large tables, 1 GB and more, MySQL indices, which are designed to speed up performance on read operations, could degrade performance on write operations.
Consider the following options to avoid a decrease in performance:
- Create CRON job, that will clean up large tables. See Find large MySQL tables in our support knowledge base for recommendations on how to identify large tables.
- For tables larger than 1 GB, use a MySQL engine optimized for logs writing. For example, the Archive engine.
- Update functionality to avoid storing logs in DB.
Oversized change log tables causing delays in entities updates in our support knowledge base.