Only commit memory on windows when initially claiming the frame #4047
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.
This fixes a fairly significant performance issue on Windows.
I was less familiar with our buffer manager when initially getting it to work on Windows. There's no need to ensure the memory is committed every time we call getFrame.
It was also necessary to skip evicted pages in updateFrameIfPageIsInFrameWithoutLock as it would otherwise segfault from trying to access uncommitted memory (it's not necessary to update them if they're evicted anyway).