1 Answer
- Newest
- Most votes
- Most comments
2
FreeableMemory decrease during mysqldump
is expected but should recover after the operation completes.
Use --single-transaction
and --quick
options to minimize memory usage during the dump.
Optimize InnoDB buffer pool settings and monitor swap usage to ensure efficient memory management.
Consider using AWS native backup solutions like automated backups or manual snapshots for less performance impact.
Monitor performance using CloudWatch and Performance Insights to identify and address any bottlenecks or issues.
Relevant content
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
Thanks, Oleksii, Giovanni!
Exactly! FreeableMemory should recover back, but it does not! When I take a dump for the 2nd or 3rd time, the application will be crashed. Therefore, I have to regularly restart RDS manually after taking Dump, so memory should be recovered back.
Can you please suggest how I can optimize InnoDB buffer pool settings?
If the buffer pool size is too large, it might not release memory as quickly. Ensure your buffer pool size is appropriately configured for your workload. SET GLOBAL innodb_buffer_pool_size = <appropriate_value>;
Ensure that your RDS instance isn't swapping, as this can drastically affect performance.
SELECT * FROM information_schema.GLOBAL_STATUS WHERE variable_name IN ('Innodb_buffer_pool_pages_data','Innodb_buffer_pool_pages_free','Innodb_buffer_pool_pages_dirty','Innodb_buffer_pool_pages_flushed');