Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
MDEV-12353 suggests one idea for improving InnoDB crash recovery speed: Read the to-be-recovered pages sorted by page number. Currently, recv_apply_hashed_log_recs() picks a ‘random’ page number from recv_sys->addr_hash and then reads a number of pages around that number.
The most straightforward way to achieve this would seem to be to replace the hash table with an ordered data structure, such as std::map, which would automatically be iterated in an ordered fashion.
While we are at it, we should merge the MDEV-12699 mlog_init_t to the same data structure.
Attachments
Issue Links
- relates to
-
MDEV-23380 InnoDB reads a page from disk despite parsing MLOG_INIT_FILE_PAGE2 record
- Closed
-
MDEV-12353 Efficient InnoDB redo log record format
- Closed
-
MDEV-12699 Improve crash recovery of corrupted data pages
- Closed
-
MDEV-27326 Mariabackup being overwhelmed during the prepare phase while using 32GB of memory
- Closed