Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5.0 -> main] Undo the temporary switch to mapped mode when loading a snapshot in mapped_private mode #1833

Merged
merged 6 commits into from
Oct 26, 2023

Conversation

greg7mdp
Copy link
Contributor

Resolves #1764

The reason I initially added this revert_to_private_mode() (so we'd load a snapshot in mapped mode, and revert to mapped_private mode after the snapshot is loaded), was that I hoped that we would only touch a few pages in normal mapped_private functioning.

The snapshot loading seemed a bad case where all state db pages containing data would be touched.

However, even in normal syncing, most of the pages are dirty after a few minutes, so the remap optimization is not worth it I believe.

@greg7mdp greg7mdp marked this pull request as draft October 26, 2023 19:26
@greg7mdp greg7mdp marked this pull request as ready for review October 26, 2023 20:05
@greg7mdp greg7mdp merged commit db254c5 into main Oct 26, 2023
@greg7mdp greg7mdp deleted the gh_1764_main branch October 26, 2023 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

segfault on leap 5.0 when starting from snapshot and database-map-mode = mapped_private
3 participants