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

MMU/MMIO performance improvements for trace production #1441

Open
OlivierBBB opened this issue Oct 18, 2024 · 0 comments
Open

MMU/MMIO performance improvements for trace production #1441

OlivierBBB opened this issue Oct 18, 2024 · 0 comments
Assignees
Labels
perf Increase performances

Comments

@OlivierBBB
Copy link
Collaborator

OlivierBBB commented Oct 18, 2024

Main point

Trace production for the MMU/MMIO is currently highly suboptimal. This is well-known to both @letypequividelespoubelles and @OlivierBBB. Here are 3 ways to handle memory:

  • current solution: full snapshots of (the EVM's) memory every time the HUB calls upon the MMU module
  • improved solution: partial snapshots of (the EVM's) memory (i.e. capturing all limbs which may be read from / written to
  • ambitious solution make no such snapshots, rather replay all memory operations at commit time

Live-tracing instructions is an option, but it would bring complications due to reverted LOG's, e.g. uncertainty about MMU/MMIO stamps. These could likely be handled, and it may represent the best alternative to the current solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
perf Increase performances
Projects
None yet
Development

No branches or pull requests

4 participants