Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
4.15.0, 5.1.0
-
None
Description
I just noticed that index updates on mutable tables retrieve their deletes (to invalidate the old index entry) one-by-one.
For batches, this can be the major time spent during an index update. The cost is mostly incured by the repeated setup (and seeking) of the new region scanner (for each row).
We can instead do a skip scan and get all updates in a single scan per region.
(Logically that is simple, but it will require some refactoring)
I won't be getting to this, but recording it here in case someone feels inclined.
