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.

Sign up for GitHub

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

Jump to bottom

Reuse the same instance of the VM for txs in block production and validation #1878

Open
xgreenx opened this issue May 2, 2024 · 0 comments · May be fixed by #1888
Open

Reuse the same instance of the VM for txs in block production and validation #1878

xgreenx opened this issue May 2, 2024 · 0 comments · May be fixed by #1888
Assignees
@Dentosal
Labels
epic An epic is a high-level master issue for large pieces of work.

Comments

@xgreenx
Copy link
Collaborator

xgreenx commented May 2, 2024

The change FuelLabs/fuel-vm#697 adds a way for a nice optimization to use the one an instance of the FuelVM for executing all transactions.

It should remove the burden on the end user to pay for the initialization of the VM.
@MitchTurner MitchTurner changed the title Reuse the same instance of the VM for the block production and validation Reuse the same instance of the VM for txs in block production and validation May 2, 2024
This was referenced May 8, 2024
Open
Draft
@xgreenx xgreenx added the epic An epic is a high-level master issue for large pieces of work. label May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Dentosal Dentosal

Labels
epic An epic is a high-level master issue for large pieces of work.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Reuse VM memory across executions FuelLabs/fuel-core
2 participants
@Dentosal @xgreenx