Hi everyone,

I'm working on optimizing a MySQL database where one of the main tables is growing quickly and receives a high volume of concurrent inserts and updates.

Currently, querying by date ranges and status flags is starting to show slow response times, but adding multiple composite indexes seems to be impacting write performance during peak hours.

For those managing similar workloads, what is the best approach to balance read vs. write performance here? Would partial indexing, table partitioning, or offloading read-heavy queries to a replica/caching layer be the better path forward?

Any advice or practical tips from your experience would be greatly appreciated!

Thanks,
Alex

Subject

Written By

Posted

Best practices for indexing large tables with frequent updates?

August 29, 2026 06:05AM