disk index: set_anticipated_count to optimally grow disk buckets at startup #31033
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
See #30711
At startup, we know how many inserts are soon coming.
This appears to cut ~15s off startup time and should greatly reduce disk i/o during startup.
This is a candidate for 1.14 if we want to enable disk index.
Summary of Changes
Tell the disk index code how many inserts are coming so that the resizing algorithm doesn't go through unnecessary incremental regrows.
This becomes very important when we stop doubling the index size each time we grow the index bucket.
Fixes #