Improve LogIterator Efficiency by Using Buffer Pool Instead of Page Allocation

[JyotinderSingh]

Currently, each LogIterator object allocates a Page to hold the log blocks it accesses. However, using a buffer from the buffer pool instead of directly allocating a page could improve efficiency, especially given that LogIterator is exclusively used by the recovery manager for rollbacks or recovery processes.

Modify LogIterator to use buffers from the buffer pool, rather than directly allocating pages. This would enable LogIterator to leverage caching mechanisms provided by the buffer pool, reducing redundant disk I/O during recovery.

We need to also think about how the buffer should be unpinned from a block.

Benefits

1. Improved Performance: Using buffers will allow recovery processes to benefit from caching, resulting in reduced disk reads and faster access to log records.
2. Simplified Resource Management: Unified use of buffers for both normal operations and recovery processes simplifies the system architecture and reduces potential code complexity.
3. Enhanced Consistency and Integrity: Leveraging buffer management mechanisms, like pin counts and dirty flags, ensures that log blocks remain in memory as needed during critical recovery operations.

[tejaswini22199]

Hey @JyotinderSingh , I would like to work on this issue. could you assign this issue to me ?

[JyotinderSingh]

Hey @JyotinderSingh , I would like to work on this issue. could you assign this issue to me ?

Thanks for your interest in this issue @tejaswini22199. I've assigned it to you.

[tejaswini22199]

Thank you @JyotinderSingh !