A company maintains a searchable repository of items in an Amazon RDS for MySQL database table with more than 10 million rows and 2 TB of General Purpose SSD storage. Millions of updates occur daily, and some insert operations are taking 10 seconds or longer due to database storage performance. Which solution addresses this performance issue?

The problem describes slow insert operations due to database storage performance on a large table with millions of daily updates. General Purpose SSD (gp2/gp3) storage offers a baseline performance with burst capabilities, but for consistently high I/O workloads, it can become a bottleneck. Provisioned IOPS SSD (io1/io2) is designed for I/O-intensive transactional workloads that require low latency, high throughput, or a high IOPS rate. Changing to Provisioned IOPS SSD directly addresses the storage performance bottleneck, improving insert operation times. Memory optimized instance classes (e.g., R-series) improve performance by providing more RAM for caching, but the issue is storage I/O, not memory capacity. Burstable performance instance classes (e.g., T-series) are not suitable for sustained high-performance workloads. Multi-AZ read replicas improve read scalability and fault tolerance but do not directly address slow write (insert) operations on the primary database.