New answers tagged amazonrds
It isn't the index size... it's the data and indexes. The InnoDB Buffer Pool: ...holds cached InnoDB data for both tables and indexes — http://dev.mysql.com/doc/refman/5.6/en/glossary.html#glos_buffer_pool The larger the buffer pool, the more InnoDB acts like an in-memory database, reading data from disk once and then accessing the data ...
Dump RDS and import it into mysql that holds all data in RAM disk: Buy strongest possible EC2 instance that might hold your database in memory twice (you might prepare everything on a small instance and then ramp it up) Create RAM disk, install and configure mysql 5.6 to hold both data and redolog on the RAM disk Stop your db-using services, dump the RDS ...
Repair by sorting is a phase that creates a temp table, populates a temp index file, and prepares all indexes for the target. This would require being in the operating system to view the temp file's size as well as the data and time stamp. If you ever need to see such progress, there are two things you can do Migrate the DB to MySQL in Amazon EC2 where ...
When you create an RDS instance, you pick an instance size, a database size, and optionally determine if you need specific IOPS. I would start by looking at the RDS monitors, and see if there are any parameters that are hitting limits. You may need to increase the instance size or IOPS to increase performance.
Also keep in mind InnoDB tables are backed up automatically daily, and recovery for InnoDB is painless, but MYISAM tables will be unrecoverable.
Top 50 recent answers are included