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

(Potential speedup) Avoid cloning snapshots #199

Open
fkrause98 opened this issue Aug 15, 2024 · 1 comment
Open

(Potential speedup) Avoid cloning snapshots #199

fkrause98 opened this issue Aug 15, 2024 · 1 comment

Comments

@fkrause98
Copy link
Contributor

Once we have everything set up to run benchmarks, we should test if avoid cloning snapshots every time we do a far_call improves performance.
An initial idea is to use a CoW pointer to only clone the snapshot when we need to mutate it.

@Oppen
Copy link
Member

Oppen commented Aug 15, 2024

The CoW is unlikely to help in all but the static calls. Most programs will end up writing something, so they will end up cloning. I think we'll need something else. That said, nicely spotted, since the flamegraphs confirm cloning snapshots are a bottleneck.

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

No branches or pull requests

2 participants