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

Improve snapshot performance for big traces #91

Open
Boyan-MILANOV opened this issue Apr 25, 2022 · 0 comments
Open

Improve snapshot performance for big traces #91

Boyan-MILANOV opened this issue Apr 25, 2022 · 0 comments
Assignees
Labels
core Maat core internals

Comments

@Boyan-MILANOV
Copy link
Collaborator

Currently snapshots record every single memory write event to be able to restore a past state. This won't scale so well on very long traces that are very memory intensive. An alternative would be to snapshot memory on a per-page basis: save the whole page when it gets written for the first time, and don't record subsequent operations affecting this page.

  • The cost for small traces is increased
  • The amount of RAM needed to take snapshots on long traces could be reduced

We should probably allow both memory snapshoting strategies to be selected as a setting for advanced users.

@Boyan-MILANOV Boyan-MILANOV added the core Maat core internals label Apr 25, 2022
@Boyan-MILANOV Boyan-MILANOV self-assigned this Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Maat core internals
Projects
None yet
Development

No branches or pull requests

1 participant