We currently only sweep the lookaside table after a drop (to free lookaside entries for dropped trees).
It would improve efficiency of reads and reduce the disk footprint of the lookaside table if we could sweep obsolete entries as well. To do this, we would need to mark which entry in the lookaside table is the on-page version. Sweep would track for each key when it has seen a stable update with a full copy of data, and could remove entries for the key after that. The on-page entry can also be removed once it is globally visible.
- causes
-
WT-3982 Fix transaction visibility bugs related to lookaside usage.
- Closed
-
WT-3891 Take the sweep walk rwlock whenever removing content from lookaside
- Closed
-
WT-5150 LAS sweep is not removing the entries that are no longer required
- Closed
- depends on
-
WT-3878 Iteration can lose its position when updating a limbo page
- Closed
-
WT-3768 Lookaside optimization: birthmarks
- Closed
- is depended on by
-
SERVER-32154 Unbounded lookaside table growth during insert workload
- Closed
-
WT-3805 Avoid reading lookaside pages in truncate fast path
- Closed
- is duplicated by
-
WT-3737 Enahance lookaside sweep to remove aged out entries
- Closed
- is related to
-
SERVER-32547 Mongo stalls while evicting dirty cache
- Closed
- related to
-
SERVER-32154 Unbounded lookaside table growth during insert workload
- Closed
- links to